Metasearching a Plurality of Servers and Placing At Least One Order

ABSTRACT

A process and system for metasearching on a distributed network activated by a request executed on a client device to request a metasearch engine to send at least one search query to a plurality of server devices, which may be search engines, the at least one search query comprising at least one keyword phrase, comprising at least one keyword, comprising incorporating, by the metasearch engine, received search results into at least one display list corresponding to the at least one keyword phrase, incorporating means for inputting at least one quantity of at least one item that may be ordered into the at least one display list, providing means for ordering the at least one item, and communicating a response to the client device.

This application is a continuation-in-part of U.S. patent applicationSer. No. 11/866,207, filed Oct. 2, 2007, which is a continuation-in-partof U.S. patent application Ser. No. 11/623,737, filed Jan. 16, 2007, nowU.S. Pat. No. 7,277,918, which is a continuation of U.S. patentapplication Ser. No. 11/023,809, filed Dec. 28, 2004, now U.S. Pat. No.7,165,091, which is a continuation of U.S. patent application Ser. No.09/791,264, filed Feb. 22, 2001, now U.S. Pat. No. 6,836,769, which is acontinuation-in-part of U.S. patent application Ser. No. 09/510,749,filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073, the full disclosuresof which all are incorporated herein by reference.

CROSS-REFERENCES

The present application is related to U.S. patent application Ser. No.11/866,207, filed Oct. 2, 2007, which is a continuation-in-part of U.S.patent application Ser. No. 11/623,737, filed Jan. 16, 2007, now U.S.Pat. No. 7,277,918, which is a continuation of U.S. patent applicationSer. No. 11/023,809, filed Dec. 28, 2004, now U.S. Pat. No. 7,165,091,which is a continuation of U.S. patent application Ser. No. 09/791,264,filed Feb. 22, 2001, now U.S. Pat. No. 6,836,769, which is acontinuation-in-part of U.S. patent application Ser. No. 09/510,749,filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073. The presentapplication is also related to U.S. patent application Ser. No.10/934,627, filed Sep. 3, 2004, now U.S. Pat. No. 7,162,511, which is acontinuation of U.S. patent application Ser. No. 09/510,749, filed Feb.22, 2000, now U.S. Pat. No. 6,789,073. The present application is alsorelated to U.S. patent application Ser. No. 10/451,128, filed Aug. 21,2002, now U.S. Pat. No. 7,165,090, which is the National StageApplication of International Application Ser. No. PCT/US01/05926, filedFeb. 22, 2001, which is a continuation-in-part of U.S. patentapplication Ser. No. 09/510,749, filed Feb. 22, 2000, now U.S. Pat. No.6,789,073. The present application is also related to Canadian patentapplication No. 2,400,926, filed Aug. 20, 2002, now Canadian Patent No.CA 2,400,926, which is the Canadian National Stage Application ofInternational Application No. PCT/US01/05926, filed Feb. 22, 2001, whichclaims the benefit of priority to U.S. patent application Ser. No.09/510,749, filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073. Thepresent application is also related to Australian patent applicationSer. No. 2001241718, filed Sep. 19, 2002, now Australian Patent No. AU2001241718, which is the Australian National Stage Application ofInternational Application No. PCT/US01/05926, filed Feb. 22, 2001, whichclaims the benefit of priority to U.S. patent application Ser. No.09/510,749, filed Feb. 22, 2000, now U.S. Pat. No. 6,789,073. Thepresent application is also related to copending European patentapplication No. EP20010912999, filed Sep. 16, 2002, which is theEuropean Regional Stage Application of International Application No.PCT/US01/05926, filed Feb. 22, 2001, which claims the benefit ofpriority to U.S. patent application Ser. No. 09/510,749, filed Feb. 22,2000, now U.S. Pat. No. 6,789,073. The above referenced documents arenot admitted to be prior art with respect to the present invention bytheir mention herein.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to clients and servers and moreparticularly to client-server multitasking.

2. Background Art

Clients, servers, and client-server systems have been known. However,there is a need for client-server multitasking. A client-servermultitasking system and process are needed, which are capable ofinformation and/or service retrieval from the same and/or different onesof servers substantially simultaneously and on-the-fly, using the sameand/or different ones of queries, and sorting, grouping, and/ororganizing responses therefrom substantially on-the-fly.

A requestor and/or user should be capable of making substantiallymultiple simultaneous same and/or different requests of the same and/ordifferent servers. The client server-multitasking system and processshould be capable of organizing responses from the servers into serviceand/or information responses, and communicating the service and/orinformation responses to the requestors and/or users substantiallysimultaneously, and on-the-fly.

The requesters and/or users should be capable of making substantiallysimultaneous service and/or information requests of the same and/ordifferent ones of servers and/or clients, using the same and/ordifferent queries, and/or the same and/or different instructions. Theclient-server multitasking system and process should be capable ofretrieving substantially multiple simultaneous services and/orinformation having the same and/or different criteria from the sameand/or different servers, sorting, grouping, and/or organizing theresponses from the servers and/or the clients into information and/orservices responses, and communicating the service and/or informationresponses to the requesters and/or the users substantiallysimultaneously. The same and/or different ones of uniform resourcelocators, target resources, and/or paths may be used.

The requesters and/or the users should be capable of making multiplesimultaneous searches. The searches should be capable of having at leastone or a plurality of same or different queries of the same and/ordifferent servers and/or clients. The responses from the servers and/orthe clients should be capable of being organized into the service and/orinformation response in a variety of formats. It should be possible tosort the responses within the service and/or information response, suchas, for example, by category, query, group, page, order of importance,ascending and/or descending order, alphabetically and/or numerically, orother characteristics, as determined by the requester, and/or the user,and/or the client-server multitasking system, or to combine theresponses within the service and/or information response, such as, forexample, interleaving the responses one with the other, such as, forexample, by order of relevance or other parameters. The responses shouldbe capable of being grouped by search criteria, server, order ofimportance, or by numerical factors such as value, price, or othernumerical quantifier. The responses should be presentable, for example,in ascending or descending order in interleaved format, such as topones, twos, threes, and so on, or presentable separately to therequestor and/or the user. The order may be order of importance orrelevance related, or, for example, numerically valued, such as price orstock market value.

The client-server multitasking system and process should be capable ofinformation and/or service retrieval from the same and/or different onesof the servers substantially simultaneously and on-the-fly, using thesame and/or different ones of the queries, and sorting, grouping, and/ororganizing responses therefrom substantially on-the-fly.

The client-server multitasking system and process should be capable ofsubstantially multiple simultaneous searching, using the same and/ordifferent ones of queries of the same and/or different ones of theclients and/or servers, which may be search engines, and/or sites,and/or servers, and/or locations on the network, and additionally and/oralternatively building a client-server multitasking search engine and/ordatabase. The client-server multitasking search engine and/or databaseshould be capable of storing the information and/or services retrievedfrom the search engines, and/or sites, and/or servers, and/or locationsbeing queried on the network, and building the client-server searchengine and/or database. The client-server multitasking search engineshould also be capable of being queried either directly and/or incombination with the substantially simultaneous searching, using thesame and/or different queries of the same and/or different searchengines, sites, servers, and/or databases. The client-servermultitasking search engine and/or database should also be capable ofupdating information and/or services stored therein by querying sites,servers, search engines, and/or databases containing information and/orservices referenced in the client-server multitasking search engineand/or database.

The client-server multitasking system and process should also be capableof use on a variety of networks, such as global area networks, and inparticular, the internet, metropolitan area networks, wide areanetworks, and local area networks.

The client-server multitasking system and process should be capable ofsubstantially simultaneous searching of the same and/or different onesof search engines and/or sites on the network substantially on-the-fly,with the same and/or different ones of the queries, and sorting,grouping, and/or organizing responses therefrom substantiallyon-the-fly.

The client-server multitasking system and process should also be capableof sorting, grouping, and/or organizing results from the servers, searchengines, and/or sites, in accordance with instructions from therequestors, and/or the users, and/or instructions resident within theclient-server multitasking system and/or process. The client-servermultitasking system and process should also be capable of drilling downand/or up to different levels within the search engines, sites, and/orservers being queried.

The client-server multitasking system and process should be capable ofproviding manual and/or timed updates. Such timed updates should allowfor motion related presentation to the requester and/or the user.

The client-server multitasking system and process should be capable ofincorporating information and/or services into a variety of userinterfaces at different locations in the user interfaces, grouping,and/or organizing the information and/or services, and optionallyeliminating duplicate information and/or services.

The client-server multitasking system and process should be capable ofincorporating links, graphics, video, text, and audio, and/orcombinations thereof, and selective advertising, according to selectablesearch, query, sorting, and/or grouping criteria, and/or combinationsthereof into the information and/or services to be delivered to the userinterfaces. The user should also be capable of placing orders, such aspurchases, and/or other types of orders, payments, confirmationsthereof, and/or combinations thereof, either directly and/or throughservers and/or sites on the network.

The client-server multitasking system should be capable of use in avariety of applications, and be capable of information comparison and/ortrend analysis of information from the same and/or different sourcessubstantially simultaneously. The client-server multitasking systemshould be capable of, for example, determining best query results, withrespect to a plurality of search engine results; purchasing and/or pricecomparisons, viewing and/or reviewing prices/values and trends fordifferent sites, determining lowest costs and lowest cost analyses forwholesale and retail purposes; product availability, e.g., airlinetickets, pricing, and ticket availability, from different airlines tothe same and/or different locations; purchasing of commodities and/orstocks form the same and/or different sites with updates every fewseconds and/or minutes; obtaining prices and/or values in differentstock markets substantially simultaneously; and searching for jobs onthe same and/or different job sites, using the same and/or different jobcriteria, for example, on a daily basis, the job sites having changingjob availability; and/or a combination thereof, all substantiallysimultaneously. The client-server multitasking system should be capableof presenting information and/or services for review and/or updatingfrom the same and/or different ones of sites, servers, and/orapplications substantially simultaneously, and trend analysis thereof,using a variety of sorting, grouping and/or organizing criteria,according to the needs of the requestor, and/or the user, and/orresident within the client-server multitasking system.

A client server-multitasking system and process are needed, which arecapable of service and/or information retrieval from at least oneserver, organization, communication, and presentation of such servicesand/or information to at least one requestor, and/or the user, and/oroptional storage, and/or retrieval of such services and/or informationfrom the optional storage. The client-server multitasking system andprocess should be capable of building a client-server multitaskingsystem search engine and/or database from responses returned from theservers, search engines, and/or sites being queried and/or searched,and/or having requests made thereof. The client-server multitaskingsystem search engine and/or database having stored information and/orservices therein should also be searchable, be capable of full textsearches thereof, and be searchable by the servers and/or the clients onthe network, either separately and/or in combination with thesubstantially simultaneous multiple same and/or different searchesand/or queries of the same and/or different servers on the network.Information in the client-server multitasking system search engineand/or database should also be searchable and/or retrievable, and shouldbe capable of being incorporated into the service and/or informationresponses delivered to the user interfaces, according to searchcriteria, selectively and/or automatically, by the requestor, and/or theuser. The client-server multitasking system search engine and/ordatabase should also be capable of spidering, and/or roboting, and/orquerying sites, services and/or information to be stored therein and/orstored in the client-server multitasking system search engine and/ordatabase, and updating the services and/or information to be storedand/or stored in the client-server multitasking system search engineand/or database.

The client-server multitasking system and process should be capable ofretrieving, parsing, processing, formatting, organizing, grouping,sorting, and consolidating services and/or information from the sameand/or different ones of the servers and/or clients having the sameand/or different structures, formats, organizations, groupings, and/ordata structures, and incorporating the parsed, processed, formatted,organized, grouped, sorted, and consolidated services and/or informationinto user responses for delivery to and use by the requesters and/orusers.

The client-server multitasking system and process should be capable ofperforming as a multiple query search engine, which performs multiplequeries of multiple sites, and performing as a single point of sale forpurchasing multiple products from multiple sources.

For the foregoing reasons, there is a need for a client-servermultitasking system and process capable of information and/or serviceretrieval from the same and/or different ones of servers substantiallysimultaneously and on-the-fly, using the same and/or different ones ofqueries of the same and/or different ones of the servers, and sorting,grouping, and/or organizing responses therefrom substantiallyon-the-fly, and communicating service and/or information responses tothe requesters and/or users substantially simultaneously and on-the-fly.The client-server multitasking system and process should be capable ofuse on a variety of networks, such as global area networks, and inparticular, the internet, metropolitan area networks, wide areanetworks, and local area networks, and be capable of searching searchengines and/or other sites substantially simultaneously and on-the-fly.The client-server multitasking system and process should be capable ofsorting, grouping, and/or organizing results from the servers, searchengines, and/or sites, in accordance with instructions from therequesters, and/or the users, and/or instructions resident within theclient-server multitasking system and/or process. The client-servermultitasking system should also be capable of use in a variety ofapplications, and be capable of information comparison and/or trendanalysis of information from the same and/or different sourcessubstantially simultaneously. The client-server multitasking system andprocess should also be capable of building a client-server multitaskingsystem search engine and/or database from responses returned from theservers, search engines, and/or sites being queried and/or searched,and/or having requests made thereof, be capable of being searched and/orqueried, querying sites referenced in the client-server multitaskingsystem search engine and/or database, and updating information and/orservices stored therein. The client-server multitasking system andprocess should be capable of retrieving, parsing, processing,formatting, organizing, grouping, sorting, and consolidating servicesand/or information from the same and/or different ones of the serversand/or clients having the same and/or different structures, formats,organizations, groupings, and/or data structures, and incorporating theparsed, processed, formatted, organized, grouped, sorted, andconsolidated services and/or information into user responses fordelivery to and use by the requestors and/or users.

SUMMARY

The present invention is directed to a client-server multitasking systemand process capable of information and/or service retrieval from thesame and/or different ones of servers substantially simultaneously andon-the-fly, using the same and/or different ones of queries of the sameand/or different ones of the servers, and sorting, grouping, and/ororganizing responses therefrom substantially on-the-fly, andcommunicating service and/or information responses to the requestersand/or users substantially simultaneously and on-the-fly. Theclient-server multitasking system and process are capable of use on avariety of networks, such as global area networks, and in particular,the internet, metropolitan area networks, wide area networks, and localarea networks, and are capable of searching search engines and/or othersites substantially simultaneously and on-the-fly.

The client-server multitasking system and process are capable ofretrieving substantially multiple simultaneous services and/orinformation having the same and/or different criteria from the sameand/or different servers, sorting, grouping, and/or organizing theresponses from the servers and/or the clients into information and/orservices responses, and communicating the service and/or informationresponses to the requesters and/or the users substantiallysimultaneously. The requesters and/or the users may make substantiallysimultaneous service and/or information requests of servers and clients,using the same and/or different queries, and/or the same and/ordifferent instructions. The same and/or different uniform resourcelocators, target resources, and/or paths may be used.

The client-server multitasking system and process are capable of makingmultiple substantially simultaneous same and/or different requests ofthe same and/or different servers, organizing responses from the serversinto service and/or information responses, and communicating the serviceand/or information responses to the requesters and/or the userssubstantially simultaneously.

The client-server multitasking system and process are also capable ofsorting, grouping, and/or organizing results therefrom the servers,search engines, and/or sites, in accordance with instructions from therequesters and/or the users, and/or instructions resident within theclient-server multitasking system and/or process. The client-servermultitasking system is capable of use in a variety of applications, andis capable of information comparison and/or trend analysis ofinformation from the same and/or different sources substantiallysimultaneously. The client-server multitasking system and process arealso capable of building a client-server multitasking system searchengine and/or database from responses returned from the servers, searchengines, and/or sites being queried and/or searched, and/or havingrequests made thereof, are capable of being searched and/or queried,querying sites referenced in the client-server multitasking systemsearch engine and/or database, and updating information and/or servicesstored therein.

The client-server multitasking system and process are capable ofinformation and/or service retrieval from the same and/or different onesof servers substantially simultaneously and on-the-fly, using the sameand/or different ones of queries, and sorting, grouping, and/ororganizing responses therefrom substantially on-the-fly.

A requester and/or user is capable of making substantially multiplesimultaneous same and/or different requests of the same and/or differentservers. The client server-multitasking system and process are capableof organizing responses from the servers into service and/or informationresponses, and communicating the service and/or information responses tothe requesters and/or the users substantially simultaneously, andon-the-fly.

The requesters and/or users are capable of making substantiallysimultaneous service and/or information requests of the same and/ordifferent ones of servers and/or clients, using the same and/ordifferent queries, and/or the same and/or different instructions. Theclient-server multitasking system and process are capable of retrievingsubstantially multiple simultaneous services and/or information havingthe same and/or different criteria from the same and/or differentservers, sorting, grouping, and/or organizing the responses from theservers and/or the clients into information and/or services responses,and communicating the service and/or information responses to therequesters and/or the users substantially simultaneously. The sameand/or different ones of uniform resource locators, target resources,and/or paths may be used.

The requesters and/or users are capable of making multiple simultaneoussearches. The searches may have at least one or a plurality of same ordifferent queries of the same and/or different servers and/or clients.The responses from the servers and/or the clients may be of beingorganized into the service and/or information response in a variety offormats. The responses may be sorted within the service and/orinformation response, such as, for example, by category, query, group,page, order of importance, ascending and/or descending order,alphabetically and/or numerically, or other characteristics, asdetermined by the requestor, and/or the user, and/or the client-servermultitasking system, and/or the responses may be combined within theservice and/or information response, such as, for example, interleavingthe responses one with the other, such as, for example, by order ofrelevance or other parameters. The responses may also be capable ofbeing grouped by search criteria, server, order of importance, or bynumerical factors such as value, price, or other numerical quantifier.The responses may be presentable, for example, in ascending ordescending order in interleaved format, such as top ones, twos, threes,and so on, or presentable separately to the requestor and/or the user.The order may be order of importance or relevance related, or, forexample, numerically valued, such as price or stock market value.

The client-server multitasking system and process are capable ofinformation and/or service retrieval from the same and/or different onesof the servers substantially simultaneously and on-the-fly, using thesame and/or different ones of the queries, and sorting, grouping, and/ororganizing responses therefrom substantially on-the-fly.

The client-server multitasking system and process are capable ofsubstantially multiple simultaneous searching, using the same and/ordifferent ones of queries of the same and/or different ones of theclients and/or servers, which may be search engines, and/or sites,and/or servers, and/or locations on the network, and additionally and/oralternatively building a client-server multitasking search engine and/ordatabase. The client-server multitasking search engine and/or databaseare capable of storing the information and/or services retrieved fromthe search engines, and/or sites, and/or servers, and/or locations beingqueried on the network, and building the client-server search engineand/or database. The client-server multitasking search engine is alsocapable of being queried either directly and/or in combination with thesubstantially simultaneous searching, using the same and/or differentqueries of the same and/or different search engines, sites, servers,and/or databases. The client-server multitasking search engine and/ordatabase are also capable of updating information and/or services storedtherein by querying sites, servers, search engines, and/or databasescontaining information and/or services referenced in the client-servermultitasking search engine and/or database.

The client-server multitasking system and process are also capable ofuse on a variety of networks, such as global area networks, and inparticular, the internet, metropolitan area networks, wide areanetworks, and local area networks.

The client-server multitasking system and process are capable ofsubstantially simultaneous searching of the same and/or different onesof search engines and/or sites on the network substantially on-the-fly,with the same and/or different ones of the queries, and sorting,grouping, and/or organizing responses therefrom substantiallyon-the-fly.

The client-server multitasking system and process are also capable ofsorting, grouping, and/or organizing results from the servers, searchengines, and/or sites, in accordance with instructions from therequesters, and/or instructions resident within the client-servermultitasking system and/or process. The client-server multitaskingsystem and process are also capable of drilling down and/or up todifferent levels within the search engines, sites, and/or servers beingqueried.

The client-server multitasking system and process are capable ofproviding manual and/or timed updates. Such timed updates allow formotion related presentation to the requester and/or the user.

The client-server multitasking system and process are capable ofincorporating information and/or services into a variety of userinterfaces at different locations in the user interfaces, grouping,and/or organizing the information and/or services, and optionallyeliminating duplicate information and/or services.

The client-server multitasking system and process are capable ofincorporating links, graphics, video, text, and audio, and/orcombinations thereof, and selective advertising, according to selectablesearch, query, sorting, and/or grouping criteria, and/or combinationsthereof into the information and/or services to be delivered to the userinterfaces. The requester and/or the user may place orders, such aspurchases, and/or other types of orders, payments, confirmationsthereof, and/or combinations thereof, either directly and/or throughservers and/or sites on the network.

The client-server multitasking system is capable of use in a variety ofapplications, and is capable of information comparison and/or trendanalysis of information from the same and/or different sourcessubstantially simultaneously. The client-server multitasking system iscapable of, for example, determining best query results, with respect toa plurality of search engine results; purchasing and/or pricecomparisons, viewing and/or reviewing prices/values and trends fordifferent sites, determining lowest costs and lowest cost analyses forwholesale and retail purposes; product availability, e.g., airlinetickets, pricing, and ticket availability, from different airlines tothe same and/or different locations; purchasing of commodities and/orstocks form the same and/or different sites with updates every fewseconds and/or minutes; obtaining prices and/or values in differentstock markets substantially simultaneously; and searching for jobs onthe same and/or different job sites, using the same and/or different jobcriteria, for example, on a daily basis, the job sites having changingjob availability; and/or a combination thereof, all substantiallysimultaneously. The client-server multitasking system is capable ofpresenting information and/or services for review and/or updating fromthe same and/or different ones of sites, servers, and/or applicationssubstantially simultaneously, and trend analysis thereof, using avariety of sorting, grouping and/or organizing criteria, according tothe needs of the requestor, and/or the user, and/or resident within theclient-server multitasking system.

The client server-multitasking system and process are capable of serviceand/or information retrieval from at least one server, organization,communication, and presentation of such services and/or information toat least one requestor and/or user, and/or optional storage, and/orretrieval of such services and/or information from the optional storage.The client-server multitasking system and process are capable ofbuilding a client-server multitasking system search engine and/ordatabase from responses returned from the servers, search engines,and/or sites being queried and/or searched, and/or having requests madethereof The client-server multitasking system search engine and/ordatabase having stored information and/or services therein are alsosearchable, are capable of full text searches thereof, and aresearchable by the servers and/or the clients on the network, eitherseparately and/or in combination with the substantially simultaneousmultiple same and/or different searches and/or queries of the sameand/or different servers on the network. Information in theclient-server multitasking system search engine and/or database are alsosearchable and/or retrievable, and are capable of being incorporatedinto the service and/or information responses delivered to the userinterfaces, according to search criteria, selectively and/orautomatically, by the requestor and/or the user. The client-servermultitasking system search engine and/or database are capable ofspidering, and/or roboting, and/or querying sites, services and/orinformation to be stored therein and/or stored in the client-servermultitasking system search engine and/or database, and updating theservices and/or information to be stored and/or stored in theclient-server multitasking system search engine and/or database.

The client-server multitasking system and process are capable ofretrieving, parsing, processing, formatting, organizing, grouping,sorting, and consolidating services and/or information from the sameand/or different ones of the servers and/or clients having the sameand/or different structures, formats, organizations, groupings, and/ordata structures, and incorporating the parsed, processed, formatted,organized, grouped, sorted, and consolidated services and/or informationinto user responses for delivery to and use by the requestors and/orusers.

The client-server multitasking system and process, then, are capable ofinformation and/or service retrieval from the same and/or different onesof servers substantially simultaneously and on-the-fly, using the sameand/or different ones of queries of the same and/or different ones ofthe servers, and sorting, grouping, and/or organizing responsestherefrom substantially on-the-fly, and communicating service and/orinformation responses to the requestors and/or users substantiallysimultaneously and on-the-fly. The client-server multitasking system andprocess are capable of use on a variety of networks, such as global areanetworks, and in particular, the internet, metropolitan area networks,wide area networks, and local area networks, and are capable ofsearching search engines and/or other sites substantially simultaneouslyand on-the-fly. The client-server multitasking system and process arecapable of sorting, grouping, and/or organizing results from theservers, search engines, and/or sites, in accordance with instructionsfrom the requesters, and/or users, and/or instructions resident withinthe client-server multitasking system and/or process. The client-servermultitasking system is capable of use in a variety of applications, andis capable of information comparison and/or trend analysis ofinformation from the same and/or different sources substantiallysimultaneously. The client-server multitasking system and process arecapable of building a client-server multitasking system search engineand/or database from responses returned from the servers, searchengines, and/or sites being queried and/or searched, and/or havingrequests made thereof, is capable of being searched and/or queried,querying sites referenced in the client-server multitasking systemsearch engine and/or database, and updating information and/or servicesstored therein. The client-server multitasking system and process arecapable of retrieving, parsing, processing, formatting, organizing,grouping, sorting, and consolidating services and/or information fromthe same and/or different ones of the servers and/or clients having thesame and/or different structures, formats, organizations, groupings,and/or data structures, and incorporating the parsed, processed,formatted, organized, grouped, sorted, and consolidated services and/orinformation into user responses for delivery to and use by therequestors and/or users.

The client-server multitasking system and process are also capable ofperforming as a multiple query search engine, which performs multiplequeries of multiple sites, and performing as a single point of sale forpurchasing multiple products from multiple sources.

A multitasking process having features of the present inventioncomprises: parsing, processing, and/or formatting a service and/orinformation request into a current request group; opening connectionswith and making at least one request of at least one server; parsing,processing, formatting, grouping, and/or organizing at least oneresponse from the at least one server into at least one addressableresponse information group; formulating information from the currentrequest group into a request pointer/address group having at least onepointer/address; formulating at least one addressable querypointer/address group having at least one other pointer/address;incorporating information and/or services from the at least oneaddressable response information group into at least one addressablequery information group; and incorporating the at least one addressablequery information group into a service and/or information response.

A client-server multitasking system having features of the presentinvention comprises: means for parsing, processing, and/or formatting aservice and/or information request into a current request group; meansfor opening connections with and making at least one request of at leastone server; means for parsing, processing, formatting, grouping, and/ororganizing at least one response from the at least one server into atleast one addressable response information group; means for formulatinginformation from the current request group into a requestpointer/address group having at least one pointer/address; means forformulating at least one addressable query pointer/address group havingat least one other pointer/address; means for incorporating informationand/or services from the at least one addressable response informationgroup into at least one addressable query information group; and meansfor incorporating the at least one addressable query information groupinto a service and/or information response.

DRAWINGS

These and other features, aspects, and advantages of the presentinvention will become better understood with regard to the followingdescription, appended claims, and accompanying drawings where:

FIG. 1 is a schematic representation of a client-server multitaskingsystem, constructed in accordance with the present invention;

FIG. 2 is a more detailed schematic representation of the client-servermultitasking system;

FIG. 3 is a schematic representation of user input UI_(n) from userU_(n) into user interface I_(n) of the client-server multitaskingsystem;

FIG. 4 is a schematic representation of a server S_(z) of theclient-server multitasking system;

FIG. 5A depicts a typical service and/or information entry request formIE_(n) at the user interface I_(n), which the user U_(n) may communicatetypical user input UI_(n) thereinto;

FIG. 5B depicts the typical service and/or information entry requestform IE_(n) at the user interface I_(n) of FIG. 5B with referencealphanumerics;

FIG. 6 depicts another typical service and/or information entry requestform IE_(n) at the user interface I_(n), which the user U_(n) maycommunicate other typical user input UI_(n) thereinto;

FIG. 7 depicts another typical service and/or information entry requestform IE_(n) at the user interface I_(n), which the user U_(n) maycommunicate other typical user input UI_(n) thereinto;

FIG. 8 depicts another typical service and/or information entry requestform IE_(n) at the user interface I_(n), which the user U_(n) maycommunicate other typical user input UI_(n) thereinto;

FIG. 9 depicts another typical service and/or information entry requestform IE_(n) at the user interface I_(n), which the user U_(n) maycommunicate other typical user input UI_(n) thereinto;

FIG. 10 depicts another typical service and/or information entry requestform IE_(n) at the user interface I_(n), which the user U_(n) maycommunicate other typical user input UI_(n) thereinto;

FIG. 11 depicts a typical completed service and/or information entryrequest form IF_(n) at the user interface I_(n);

FIG. 12 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 13 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 14A depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 14B depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 14C depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 15 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 16 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 17 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 18 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 19 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 20 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 21 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 22 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 23 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 24 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 25 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIG. 26 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 27A, 27B, and 27C depict a typical user response UR_(n), as atypical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 28A, 28B, and 28C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 29A, 29B, and 29C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 30A and 30B depict another typical user response UR_(n), as thetypical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 31A and 31B depict another typical user response UR_(n), as thetypical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 32A and 32B depict another typical user response UR_(n), as thetypical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 33A, 33B, and 33C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 34A, 34B, and 34C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 35A, 35B, and 35C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 36A, 36B, and 36C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 37A, 37B, 37C, and 37D depict another typical user responseUR_(n), as the typical service and/or information response form IS_(n)at the user interface I_(n), which may be communicated to the userU_(n), illustrated in partial views;

FIGS. 38A, 38B, 38C, and 38D depict another typical user responseUR_(n), as the typical service and/or information response form IS_(n)at the user interface I_(n), which may be communicated to the userU_(n), illustrated in partial views;

FIGS. 39A, 39B, and 39C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 40A, 40B, 40C, 40D, 40E, 40F, 40G, 40H, 40I, 40J, 40K, 40L, and40M depict another typical user response UR_(n), as the typical serviceand/or information response form IS_(n) at the user interface I_(n),which may be communicated to the user U_(n), illustrated in partialviews;

FIGS. 41A, 41B, 41C, 41D, 41E, and 41F depict another typical userresponse UR_(n), as the typical service and/or information response formIS_(n) at the user interface I_(n), which may be communicated to theuser U_(n), illustrated in partial views;

FIGS. 42A, 42B, 42C, 42D, 42E, 42F, 42G, 42H, 42I, 42J, 42K, 42L, 42M,42N, and 42O depict another typical user response UR_(n), as the typicalservice and/or information response form IS_(n) at the user interfaceI_(n), which may be communicated to the user U_(n), illustrated inpartial views;

FIGS. 43A, 43B, 43C, 43D, 43E, 43F, 43G, 43H, 43I, 43J, 43K, 43L, 43M,43N, and 43O depict another typical user response UR_(n), as the typicalservice and/or information response form IS_(n) at the user interfaceI_(n), which may be communicated to the user U_(n), illustrated inpartial views;

FIGS. 44A, 44B, and 44C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 45A, 45B, and 45C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 46A, 46B, 46C, 46D, and 46E depict another typical user responseUR_(n), as the typical service and/or information response form IS_(n)at the user interface I_(n), which may be communicated to the userU_(n), illustrated in partial views;

FIGS. 47A, 47B, and 47C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIGS. 48A, 48B, 48C, and 48D depict another typical user responseUR_(n), as the typical service and/or information response form IS_(n)at the user interface I_(n), which may be communicated to the userU_(n), illustrated in partial views;

FIGS. 49A, 49B, 49C, 49D, 49E, 49F, 49G, 49H, and 49I depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views;

FIGS. 50A, 50B, 50C, 50D, 50E, 50F, 50G, 50H, 50I, 50J, and 50K depictanother typical user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), illustrated in partial views;

FIGS. 51A, 51B, 51C, 51D, 51E, 51F, and 51G depict another typical userresponse UR_(n), as the typical service and/or information response formIS_(n) at the user interface I_(n), which may be communicated to theuser U_(n), illustrated in partial views;

FIGS. 52A, 52B, and 52C depict another typical user response UR_(n), asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n),illustrated in partial views;

FIG. 53A is a schematic representation of a server PS of theclient-server multitasking system having an optional database;

FIG. 53B is a schematic representation of a client C_(n) of theclient-server multitasking system having an optional database;

FIG. 54 is a schematic representation of a particular one of the clientsC₁ . . . C_(n) of the client-server multitasking system, designated asthe particular client C_(n), communicating with ones of the servers S₁ .. . S_(z), in accordance with the designation scheme corresponding tothe corresponding ones of the server designations S_(n1) . . . S_(nm),corresponding to the requests Q_(n1) . . . Q_(nm), through the serverPS;

FIG. 55 is a schematic representation of the particular client C_(n) ofthe client-server multitasking system communicating with ones of theservers S₁ . . . S_(z), in accordance with the designation schemecorresponding to the corresponding ones of the server designationsS_(n1) . . . S_(nm), corresponding to the requests Q_(n1) . . . Q_(nm);

FIG. 56 is a schematic representation of the particular client C_(n) ofthe client-server multitasking system communicating with ones of theservers S₁ . . . S_(z), in accordance with the designation schemecorresponding to the corresponding ones of the server designationsS_(n1) . . . S_(nm), corresponding to the requests Q_(n1) . . . Q_(nm),and also through the server PS;

FIG. 57 is an alternate schematic representation of the client-servermultitasking system of FIG. 1, constructed in accordance with thepresent invention, regrouped diagrammatically and alternatively namedfor illustrative purposes only, to illustrate and visualize possibletypical communication paths;

FIG. 58 is a schematic representation of a particular service and/orinformation request IQ_(n);

FIG. 59 is a schematic representation of a particular service and/orinformation request IQ_(n) parsed, processed, and/or formatted into acurrent request group QA_(nc) request groups QA_(n1) . . . QA_(nz), andcorresponding optional instructions VJ_(n1) . . . VJ_(nk), andutilization of information therefrom to make the requests Q_(n1) . . .Q_(nm), obtain the responses R_(n1) . . . R_(nm), and incorporateinformation therefrom into a particular service and/or informationresponse IR_(n);

FIG. 60 is a schematic representation of the particular service and/orinformation request IQ_(n) parsed, processed, and/or formatted into acurrent request group QA_(nc), request groups QA_(n1) . . . QA_(nz), andcorresponding optional instructions VJ_(n1) . . . VJ_(nk), andutilization of information therefrom to make the requests Q_(n1) . . .Q_(nm), obtain the responses R_(n1) . . . R_(nm), and incorporateinformation therefrom into the particular service and/or informationresponse IR_(n), having other grouping/sorting that may be usedadditionally and/or alternatively to that of FIG. 59;

FIG. 61 is a schematic representation of the particular service and/orinformation response IR_(n) having a service and/or information groupG_(n), additional request links SL_(n1) . . . SL_(nw), optional orderform, optional additional advertisements and/or links, optional hiddeninformation, and the optional service and/or information entry requestform;

FIG. 62 is a schematic representation of a particular user serviceand/or information request iq_(n);

FIG. 63 is a schematic representation of a particular user serviceand/or information request iq_(n) parsed, processed, and/or formattedinto the current request group QA_(nc), the request groups QA_(n1) . . .QA_(nz), and the corresponding optional instructions VJ_(n1) . . .VJ_(nk), and utilization of information therefrom to make the requestsQ_(n1) . . . Q_(nm), obtain the responses R_(n1) . . . R_(nm), andincorporate information therefrom into the particular user serviceand/or information response ir_(n);

FIG. 64 is a schematic representation of the particular user serviceand/or information request iq_(n) parsed, processed, and/or formattedinto the current request group QA_(nc), the request groups QA_(n1) . . .QA_(nz), and the corresponding optional instructions VJ_(n1) . . .VJ_(nk), and utilization of information therefrom to make the requestsQ_(n1) . . . Q_(nm), obtain the responses R_(n1) . . . R_(nm), andincorporate information therefrom into the particular user serviceand/or information response ir_(n), having other grouping/sorting thatmay be used additionally and/or alternatively to that of FIG. 63;

FIG. 65 is a schematic representation of the particular user serviceand/or information response ir_(n) having the service and/or informationgroup G_(n), the additional request links SL_(n1) . . . SL_(nw), theoptional order form, the optional additional advertisements and/orlinks, the optional hidden information, and the optional service and/orinformation entry request form;

FIG. 66A is a schematic representation of a response information groupRG_(nm) having addressable individual information groups LG_(nm1) . . .LG_(nmr) showing optional addressable pointer/address indices IN_(nm1) .. . IN_(nmr) correspondingly associated with optional addressableindividual information groups LG_(nm1) . . . LG_(nmr), which may beaddressed/pointed with pointer/address PP_(nm1);

FIG. 66B is a schematic representation of the addressable responseinformation group RG_(nm) having the addressable individual informationgroups LG_(nm1) . . . LG_(nmr) showing the optional addressablepointer/address indices IN_(nm1) . . . IN_(nmr) correspondinglyassociated with the optional addressable individual information groupsLG_(nm1) . . . LG_(nmr), which may be addressed/pointed with thepointer/address PP_(nm2);

FIG. 66C is a schematic representation of the addressable responseinformation group RG_(nm) having the addressable individual informationgroups LG_(nm1) . . . LG_(nmr) showing the optional addressablepointer/address indices IN_(nm1) . . . IN_(nmr) correspondinglyassociated with the optional addressable individual information groupsLG_(nm1) . . . LG_(nmr), which may be addressed/pointed with thepointer/address PP_(nmr);

FIG. 67 is a schematic representation of the individual informationgroups LG_(nm1) . . . LG_(nmr) having corresponding optional linksLD_(nm1) . . . LD_(nmr), and/or corresponding optional descriptionsDD_(nm1) . . . DD_(nmr), and/or corresponding optional prices/valuesPD_(nm1) . . . PD_(nmr), and/or corresponding optional images ID_(nm1) .. . ID_(nmr);

FIG. 68 is a schematic representation of a labelled individualinformation group LL_(nmr);

FIG. 69 is a schematic representation of an addressable queryinformation group GI_(nz);

FIG. 70 is a schematic representation of steps of a client-servermultitasking process of the present invention;

FIG. 71 is a schematic representation of a multitasking process ofderiving the service and/or information response IR_(n) and/or the userservice and/or information response ir_(n), with reference to FIGS. 59and 63;

FIG. 72 is a schematic representation of a multitasking process ofderiving the service and/or information response IR_(n) and/or the userservice and/or information response ir_(n) having other grouping/sortingthat may be used additionally and/or alternatively to that of FIGS. 59and 63, as shown with reference to FIGS. 60 and 64;

FIG. 73 is a schematic representation of a step of the multitaskingprocess of FIGS. 71 and 72 shown in more detail;

FIG. 74 is a schematic representation of another step of themultitasking process of FIG. 71 shown in more detail;

FIG. 75 is a schematic representation of another step of themultitasking process of FIG. 72 shown in more detail;

FIG. 76 is a schematic representation of user review of user responseUR_(n) and/or selection of additional services and/or information;

FIG. 77 is a schematic representation of the user input UI_(n) into theservice and/or information entry request form IE_(n);

FIG. 78 is a schematic representation of the service and/or informationentry request form IE_(n) showing fields, links, and elements of theservice and/or information entry request form IE_(n);

FIG. 79 is a schematic representation of a completed service and/orinformation entry request form IF_(n) showing typical elements, values,and field names;

FIG. 80 is a schematic representation of the completed service and/orinformation entry request form IF_(n), a user service and/or informationrequest iq_(n), and the client C_(n) of the client-server multitaskingsystem;

FIG. 81 is a schematic representation of the user service and/orinformation request iq_(n);

FIG. 82 is a schematic representation of the service and/or informationrequest IQ_(n);

FIG. 83 is an alternate schematic representation of the user serviceand/or information request iq_(n) of FIG. 81;

FIG. 84 is an alternate schematic representation of the service and/orinformation request IQ_(n) of FIG. 82;

FIG. 85 is a more detailed schematic representation of the serviceand/or information request IQ_(n) of FIGS. 82 and 84 showing typicalfield names and values;

FIG. 86 is an alternate more detailed schematic representation of theservice and/or information request IQ_(n) of FIGS. 82 and 84;

FIG. 87 is a schematic representation showing queries QQ_(n1) . . .QQ_(nm) and corresponding server addresses AQ_(n1) . . . AQ_(nm);

FIG. 88 shows the schematic representation of FIG. 87 having typicalvalues;

FIG. 89 shows the schematic representation of FIG. 87 having othertypical values;

FIG. 90 shows the schematic representation of FIG. 87 having othertypical values;

FIG. 91 shows the schematic representation of FIG. 87 having othertypical values;

FIG. 92 is a schematic representation of information that may be usedfor formulating a typical particular one of the requests Q_(n1) . . .Q_(nm), designated as the request Q_(nm), and optional instructionsVJ_(nm1) . . . VJ_(nk) from the particular service and/or informationrequest IQ_(n) and opening a connection OC_(nm);

FIG. 93 is a schematic representation of information that may be usedfor formulating the typical particular one of the requests Q_(n1) . . .Q_(nm), designated as the request Q_(nm), and the optional instructionsVJ_(nm1) . . . VJ_(nk) from the particular user service and/orinformation request iq_(n) and opening the connection OC_(nm);

FIG. 94 is an alternate schematic representation of information that maybe used for formulating the typical particular one of the requestsQ_(n1) . . . Q_(nm), designated as the request Q_(nm), and optionalinstructions VJ_(nm1) . . . VJ_(nk) from the particular service and/orinformation request IQ_(n) and opening a connection OC_(nm) of FIG. 92;

FIG. 95 is an alternate schematic representation of information that maybe used for formulating the typical particular one of the requestsQ_(n1) . . . Q_(nm), designated as the request Q_(nm), and the optionalinstructions VJ_(nm1) . . . VJ_(nk) from the particular user serviceand/or information request iq_(n) and opening the connection OC_(nm) ofFIG. 93;

FIG. 96 is a schematic representation of queries QQ_(n1) . . . QQ_(nm),corresponding server addresses AQ_(n1) . . . AQ_(nm), and optionalinstructions VJ_(nm1) . . . VJ_(nk) that may be parsed, processed,and/or formatted from the service and/or information request IQ_(n)and/or the user service and/or information request iq_(n);

FIG. 97 is a schematic representation of a request pointer/address groupQZ_(ns), having a particular one of query pointer/address groups QG_(n1). . . QG_(nz), designated as the query pointer/address group QG_(nz),associated ones of the addressable response information groups RG_(n1) .. . RG_(nm), the pointers/addresses PP_(n11) . . . PP_(nmr), and thequery information group GI_(nz) associated with the querypointer/address group QG_(nz);

FIG. 98 is a schematic representation of a sorting criteria addressingscheme having a particular query pointer/address group QG_(nz),associated ones of response information groups RG_(nm), and queryinformation group GI_(nz) associated with the query pointer/addressgroup QG_(nz);

FIG. 99 is a schematic representation of an alternate sorting criteriaaddressing scheme having a particular query pointer/address groupQG_(nz), associated ones of response information groups RG_(nm), andquery information group GI_(nz) associated with the querypointer/address group QG_(nz);

FIG. 100 is a schematic representation of typical ones of the querypointer/address groups QG_(n1) . . . QG_(nz), having the sortingcriteria addressing scheme of FIG. 98, having typical ones of queriesQQ_(n1) . . . QQ_(nz) and corresponding server addresses AQ_(n1) . . .AQ_(nz) associated therewith;

FIG. 101 is another schematic representation of the typical ones of thequery pointer/address groups QG_(n1) . . . QG_(nz), having the sortingcriteria addressing scheme of FIG. 98, having the typical ones of the ofqueries QQ_(n1) . . . QQ_(nz) and the corresponding ones of the serveraddresses AQ_(n1) . . . AQ_(nz) of FIG. 100 associated therewith;

FIG. 102 is a generic schematic representation of the querypointer/address groups QG_(n1) . . . QG_(nz), having the sortingcriteria addressing scheme of FIG. 98, having the ones of queriesQQ_(n1) . . . QQ_(nz) and the corresponding ones of the server addressesAQ_(n1) . . . AQ_(nz) associated therewith;

FIG. 103 is a schematic representation of a request Q_(nm) of theclient-server multitasking system;

FIG. 104 is a schematic representation of a response R_(nm) of theclient-server multitasking system;

FIG. 105 is a schematic representation of an entity body RH_(nm) of theresponse R_(nm) of FIG. 104 having optional response individualinformation groups LS_(nm1) . . . LS_(nmr), and/or optional informationLI_(nm);

FIG. 106 is a schematic representation of the addressable responseinformation group RG_(nm) having the addressable individual informationgroups LG_(nm1) . . . LG_(nmr) parsed, and/or processed, and/orformatted, and/or organized, and/or grouped into the addressableresponse information group RG_(nm) from the optional entity body RH_(nm)of FIG. 105;

FIG. 107 is a schematic representation of the optional responseindividual information group LS_(nmr) parsed, and/or processed, and/orformatted, and/or organized, and/or grouped into the addressableindividual information group LG_(nmr);

FIG. 108 is a schematic representation of the optional links LD_(nm1) .. . LD_(nmr), and/or the optional descriptions DD_(nm1) . . . DD_(nmr),and/or the optional prices/values PD_(nm1) . . . PD_(nmr), and/or theoptional images ID_(nm1) . . . ID_(nmr) parsed individually and/orseparately, and incorporated into the addressable response informationgroup RG_(nm) from the optional entity body RH_(nm);

FIG. 109 is a schematic representation of a typical one of theaddressable query information group GI_(nz), based upon certain sortingand/or grouping criteria, having the labelled individual informationgroups LL_(nz1) . . . LL_(nzu), the optional database labelledindividual information groups RL_(nz1) . . . RL_(nzx), the optionalquery description QT_(nz), the optional server descriptions and/or linksST_(nz1) . . . ST_(nzf), and the optional advertisements and/or linksLT_(nz1) . . . LT_(nzt) incorporated into certain typical ones of thetypical service and/or information response forms IS_(n) of FIGS.27A-52C, inclusive;

FIG. 110 is another schematic representation of a typical one of theaddressable query information group GI_(nz), based upon certain sortingand/or grouping criteria, having the labelled individual informationgroups LL_(nz1) . . . LL_(nzu), the optional database labelledindividual information groups RL_(nz1) . . . RL_(nzx), the optionalquery description QT_(nz), the optional server descriptions and/or linksST_(nz1) . . . ST_(nzf), and the optional advertisements and/or linksLT_(nz1) . . . LT_(nzt) incorporated into certain typical ones of thetypical service and/or information response forms IS_(n) of FIGS.27A-52C, inclusive;

FIG. 111 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 112A, 112B, 112C, 112D, 112E, 112F, 112G, and 112H depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views;

FIG. 113 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 114A, 114B, 114C, 114D, 114E, 114F, 114G, and 114H depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views;

FIG. 115 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 116A, 116B, 116C, 116D, 116E, 116F, 116G, and 116H depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views;

FIG. 117 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 118A, 118B, 118C, 118D, 118E, 118F, 118G, and 118H depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views;

FIG. 119 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 120A, 120B, 120C, 120D, 120E, 120F, 120G, and 120H depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views;

FIG. 121 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 122A, 122B, 122C, 122D, 122E, 122F, 122G, and 122H depict atypical combined user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), and an order entry form OF_(n), whichthe user U_(n) may use to enter an order, illustrated in partial views;

FIGS. 123A, 123B, 123C, 123D, 123E, 123F, 123G, and 123H depict thetypical combined user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), and the order entry form OF_(n),which the user U_(n) may use to enter the order, of FIGS. 114A-114H,with typical order information entered therein, illustrated in partialviews;

FIGS. 124A and 124B depict a typical preview form of an order OP_(n),resulting from submission of the order entry form OF_(n), of the typicalcombined user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), and the order entry form OF_(n), whichthe user U_(n) may use to enter the order, of FIGS. 114A-114H, with thetypical order information entered therein, as shown in FIGS. 123A-123H,illustrated in partial views;

FIGS. 125A and 125B depict a typical order placement form OL_(n), havingthe typical preview form of the order OP_(n), resulting from submissionof the order entry form OF_(n), of the typical combined user responseUR_(n), as the typical service and/or information response form IS_(n)at the user interface I_(n), which may be communicated to the userU_(n), and the order entry form OF_(n), which the user U_(n) may use toenter the order, of FIGS. 114A-114H, with the typical order informationentered therein, as shown in FIGS. 123A-123H, or which the user U_(n)may enter through the typical preview form of the order OP_(n) of FIGS.124A and 124B, illustrated in partial views;

FIGS. 126A and 126B depict a typical completed order placement formOL_(n), having a preview of the order OP_(n), resulting from submissionof the order entry form OF_(n), of the typical combined user responseUR_(n), as the typical service and/or information response form IS_(n)at the user interface I_(n), which may be communicated to the userU_(n), and the order entry form OF_(n), which the user U_(n) may use toenter the order, of FIGS. 114A-114H, with the typical order informationentered therein, as shown in FIGS. 123A-123H, or which the user U_(n)may enter through the typical preview form of the order OP_(n) of FIGS.124A and 124B, illustrated in partial views;

FIGS. 127A and 127B depict a typical order confirmation OC_(n),resulting from submission of the typical completed order placement formOL_(n) of FIGS. 126A and 126B, illustrated in partial views;

FIGS. 128A, 128B, and 128C depict a typical e-mail order placementEP_(n), resulting from submission of the typical completed orderplacement form OL_(n) of FIGS. 126A and 126B, illustrated in partialviews;

FIGS. 129A, 129B, and 129C depict a typical e-mail confirmation ofreceipt of order EC_(n), resulting from submission of the typicalcompleted order placement form OL_(n) of FIGS. 126A and 126B,illustrated in partial views;

FIGS. 130A and 130B depict a typical e-mail order placement EP_(n) of aportion of the order, resulting from submission of the typical completedorder placement form OL_(n) of FIGS. 126A and 126B, illustrated inpartial views;

FIGS. 131A and 131B depict a typical e-mail order placement EP_(n) ofanother portion of the order, resulting from submission of the typicalcompleted order placement form OL_(n) of FIGS. 126A and 126B,illustrated in partial views;

FIGS. 132A and 132B depict a typical e-mail order placement EP_(n) ofanother portion of the order, resulting from submission of the typicalcompleted order placement form OL_(n) of FIGS. 126A and 126B,illustrated in partial views;

FIG. 133 is a schematic representation of certain typical optionalinstructions VJ_(nm1) . . . VJ_(nk) and/or certain additional requestlinks SL_(n1) . . . SL_(nw);

FIG. 134 is a schematic representation of other certain typical optionalinstructions VJ_(nm1) . . . VJ_(nk) and/or other certain additionalrequest links SL_(n1) . . . SL_(nw);

FIG. 135 depicts certain typical additional request links SL_(n1) . . .SL_(nw);

FIG. 136 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) therethrough;

FIG. 137 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) therethrough;

FIG. 138 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) therethrough;

FIG. 139 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) therethrough;

FIG. 140 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) therethrough;

FIG. 141 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) therethrough;

FIG. 142 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 143A, 143B, 143C, 143D, 143E, 143F, 143G, and 143H depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views;

FIG. 144 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 145A, 145B, 145C, 145D, 145E, 145F, and 145G depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views;

FIG. 146 depicts another typical completed service and/or informationentry request form IF_(n) at the user interface I_(n);

FIGS. 147A, 147B, 147C, 147D, 147E, 147F, and 147G depict anothertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), illustrated in partial views.

FIG. 148 is a schematic representation of a particular service and/orinformation request IQ_(n) parsed, processed, and/or formatted into acurrent request group QA_(nc), request groups QA_(n1) . . . QA_(nz), andcorresponding optional instructions VJ_(n1) . . . VJ_(nk), andutilization of information therefrom to make the requests Q_(n1) . . .Q_(nm), obtain the responses R_(n1) . . . R_(nm), and incorporateinformation therefrom into a particular service and/or informationresponse IR_(n);

FIG. 149 is a schematic representation of a particular service and/orinformation request IQ_(n) parsed, processed, and/or formatted into acurrent request group QA_(nc) and corresponding optional instructionsVJ_(n1) . . . VJ_(nk), and utilization of information therefrom to makethe requests Q_(n1) . . . Q_(nm), obtain the responses R_(n1) . . .R_(nm), and incorporate information therefrom into a particular serviceand/or information response IR_(n);

FIG. 150 is a schematic representation of a particular service and/orinformation group G_(n) associated with a typical securitiestransaction, showing query information groups GI_(n1) . . . GI_(nz)represented as a plurality of order books OB_(n1) . . . OB_(nz) at theuser interface I_(n) for a plurality of securities, stocks, financialproducts, financial instruments, stocks, commodities, and/or currencies;and

FIG. 151 is a schematic representation of a particular service and/orinformation group G_(n) associated with a typical securitiestransaction, showing the query information group GI_(nz) represented asthe order book OB_(nz) at the user interface I_(n) for a security,stock, financial product, financial instrument, commodity, and/orcurrency.

DESCRIPTION

The preferred embodiments of the present invention will be describedwith reference to FIGS. 1-150 of the drawings. Identical elements in thevarious figures are identified with the same reference alphanumerics.

I. System

A. Overview

FIGS. 1 and 2 show a client-server multitasking system 10 of the presentinvention, having requesters U₁ . . . U_(n) (12), hereinafter calledusers U₁ . . . U_(n) (12), corresponding user interfaces I₁ . . . I_(n)(14), corresponding clients C₁ . . . C_(n) (16), server PS (18), serversS₁ . . . S_(z) (20), and optional servers SO₁ . . . SO_(p) (22),constructed in accordance with the present invention, which reside on anetwork 24. Each of the users U₁ . . . U_(n) (12) communicate with thecorresponding clients C₁ . . . C_(n) (16) through the corresponding userinterfaces I₁ . . . I_(n) (14).

Each of the users U₁ . . . U_(n) (12) enter corresponding user inputsUI₁ . . . UI_(n) (25) having one or more same and/or different userrequests qu₁₁ . . . qu_(nu) (26) into the corresponding user interfacesI₁ . . . I_(n) (14), as shown in FIG. 3. The user requests qu₁₁ . . .qu_(nu) (26) are communicated from the user interfaces I₁ . . . I_(n)(14) to the corresponding clients C₁ . . . C_(n) (16) withincorresponding user service and/or information requests iq₁ . . . iq_(n)(27), having the user requests qu₁₁ . . . qu_(nu) (26) and otheroptional information. The users U₁ . . . U_(n) (12) may enter thecorresponding user inputs UI₁ . . . UI_(n) (25) at the same and/ordifferent times.

Each of the user interfaces I₁ . . . I_(n) (14) communicate the userservice and/or information requests iq₁ . . . iq_(n) (27) to thecorresponding clients C₁ . . . C_(n) (16), which optionally format thecorresponding user service and/or information requests iq₁ . . . iq_(n)(27) into corresponding service and/or information requests IQ₁ . . .IQ_(n) (28), as required. Each of the service and/or informationrequests IQ₁ . . . IQ_(n) (28) have information therein that may be usedto formulate one or more same and/or different requests Q₁₁ . . . Q_(nm)(29) to be made of one or more of the same and/or different ones of theservers S₁ . . . S_(z) (20), which may hereinafter be called serverdesignations S₁₁ . . . S_(nm) (30), in accordance with a designationscheme which designates the servers S₁ . . . S_(z) (20) to becommunicated with corresponding to the requests Q₁₁ . . . Q_(nm) (29) asthe corresponding server designations S₁₁ . . . S_(nm) (30), as shown inFIGS. 2 and 4. FIG. 4 shows the server designations S₁₁ . . . S_(nm)(30) for typical ones of the requests Q₁₁ . . . Q_(nm) (29) and atypical one of the servers S_(z) (20). Each of the requests Q₁₁ . . .Q_(nm) (29) may be the same and/or different one from the other and maybe made of the same and/or different ones of the servers S₁ . . . S_(z)(20) at the same time and/or different times.

Each of the service and/or information requests IQ₁ . . . IQ_(n) (28)may be communicated to the server PS (18), which parses, processes,and/or formats the service and/or information requests IQ₁ . . . IQ_(n)(28) into the requests Q₁₁ . . . Q_(nm) (29).

The corresponding clients C₁ . . . C_(n) (16) may also and/oralternatively optionally parse, process, and/or format the correspondinguser service and/or information requests iq₁ . . . iq_(n) (27) into oneor more of the same and/or different requests Q₁₁ . . . Q_(nm) (29) tobe made of one or more of the same and/or different ones of the serversS₁ . . . S_(z) (20), in accordance with the designation schemecorresponding to the corresponding ones of the server designations S₁₁ .. . S_(nm) (30), as required.

Certain ones of the clients C₁ . . . C_(n) (16) may communicatecorresponding certain ones of the service and/or information requestsIQ₁ . . . IQ_(n) (28) to the server PS (18), which parses, processesand/or formats the certain ones of the service and/or informationrequests IQ₁ . . . IQ_(n) (28) into certain ones of the requests Q₁₁ . .. Q_(nm) (29), as required, and communicates the certain ones of therequests Q₁₁ . . . Q_(nm) (29) to the servers S₁ . . . S_(z) (20), inaccordance with the designation scheme corresponding to thecorresponding certain ones of the server designations S₁₁ . . . S_(nm)(30).

Alternate ones of the clients C₁ . . . C_(n) (16) may communicatecorresponding alternate ones of the requests Q₁₁ . . . Q_(nm) (29) tocorresponding alternate ones of the servers S₁ . . . S_(z) (20), inaccordance with the designation scheme corresponding to thecorresponding alternate ones of the server designations S₁₁ . . . S_(nm)(30).

Other alternate ones of the clients C₁ . . . C_(n) (16) may communicatecorresponding other alternate ones of the service and/or informationrequests IQ₁ . . . IQ_(n) (28) to the server PS (18), which parses,processes and/or formats the other alternate ones of the service and/orinformation requests IQ₁ . . . IQ_(n) (28) into other alternate ones ofthe requests Q₁₁ . . . Q_(nm) (29), as required, communicates the otheralternate ones of the requests Q₁₁ . . . Q_(nm) (29) to correspondingother alternate ones of the servers S₁ . . . S_(z) (20), in accordancewith the designation scheme corresponding to the corresponding otheralternate ones of the server designations S₁₁ . . . S_(nm) (30); andadditionally the other alternate ones of the clients C₁ . . . C_(n) (16)may also parse, process, and/or format the user service and/orinformation requests iq₁ . . . iq_(n) (27) into one or more of the sameand/or different yet other alternate ones of the requests Q₁₁ . . .Q_(nm) (29), and communicate the yet other alternate ones of therequests Q₁₁ . . . Q_(nm) (29) to corresponding yet other alternate onesof the servers S₁ . . . S_(z) (20), in accordance with the designationscheme corresponding to the corresponding yet other alternate ones ofthe server designations S₁₁ . . . S_(nm) (30).

Each of the service and/or information requests IQ₁ . . . IQ_(n) (28)may, thus, be communicated from the corresponding clients C₁ . . . C_(n)(16) to the server PS (18). The requests Q₁₁ . . . Q_(nm) (29) may becommunicated from the server PS (18) and/or from the correspondingclients C₁ . . . C_(n) (16) to the servers S₁ . . . S_(z) (20), and maydepend upon instructions from and/or generated by the correspondingusers U₁ . . . U_(n) (12), and/or the corresponding user interfaces I₁ .. . I_(n) (14) and/or the corresponding clients C₁ . . . C_(n) (16),and/or information generated by the server PS (18) and/or the servers S₁. . . S_(z) (20), and/or ancillary instructions, a combination thereof,and/or other suitable means.

Each of the servers S₁ . . . S_(z) (20) corresponding to the designationscheme S₁₁ . . . S_(nm) (30) replies to the server PS (18) and/or theclients C₁ . . . C_(n) (16), accordingly, and communicates correspondingresponses R₁₁ . . . R_(nm) (32), associated with the requests Q₁₁ . . .Q_(nm) (29), to the server PS (18) and/or the clients C₁ . . . C_(n)(16) making the requests Q₁₁ . . . Q_(nm) (29), as shown in FIG. 2 fortypical ones of the requests Q₁₁ . . . Q_(nm) (29) and the correspondingresponses R₁₁ . . . R_(nm) (32).

The server PS (18) and/or the appropriate clients C₁ . . . C_(n) (16)parse, process, format, sort, group, and/or organize the responses R₁₁ .. . R_(nm) (32) into corresponding service and/or information responsesIR₁ . . . IR_(n) (34), having corresponding parsed, processed,formatted, sorted, grouped, and/or organized service and/or informationgroups G₁ . . . G_(n) (35) (shown later in FIGS. 27A-52C, inclusive)acceptable to the corresponding clients C₁ . . . C_(n) (16) and thecorresponding respective user interfaces I₁ . . . I_(n) (14). The serverPS (18) communicates the appropriate service and/or informationresponses IR₁ . . . IR_(n) (34) to the corresponding clients C₁ . . .C_(n) (16).

The clients C₁ . . . C_(n) (16) format the service and/or informationresponses IR₁ . . . IR_(n) (34) into corresponding user service and/orinformation responses ir₁ . . . ir_(n) (36), as required, andcommunicate the user service and/or information responses ir₁ . . .ir_(n) (36) to the corresponding user interfaces I₁ . . . I_(n) (14).The user interfaces I₁ . . . I_(n) (14) incorporate the user serviceand/or information responses ir₁ . . . ir_(n) (36) into correspondinguser responses UR₁ . . . UR_(n) (37), which are derived at the userinterfaces I₁ . . . I_(n) (14), and communicated by the user interfacesI₁ . . . I_(n) (14) to the corresponding users U₁ . . . U_(n) (12). Theusers U₁ . . . U_(n) (12) review the corresponding user responses UR₁ .. . UR_(n) (37) at the user interfaces I₁ . . . I_(n) (14) and/or selectadditional services and/or information therefrom.

B. Typical Service and/or Information Entry Request Forms

FIGS. 5A, 5B, and 6-10 show typical ones of service and/or informationentry request forms IE₁ . . . IE_(n) (38) at the user interfaces I₁ . .. I_(n) (14), which the users U₁ . . . U_(n) (12) may communicatetypical ones of the user inputs UI₁ . . . UI_(n) (25) thereinto, asrequests for information and/or services. The typical ones of theservice and/or information entry request forms IE₁ . . . IE_(n) (38) atthe user interfaces I₁ . . . I_(n) (14) shown in FIGS. 5A, 5B, and 6-10are typical examples of the service and/or information entry requestforms IE₁ . . . IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14),a much larger variety of which is possible. Names and/or links and/orother information are incorporated into the typical ones of the serviceand/or information entry request forms IE₁ . . . IE_(n) (38) shown inFIGS. 5A, 5B, and 6-10 for illustrative purposes, and are not intendedto limit the large variety of the service and/or information entryrequest forms IE₁ . . . IE_(n) (38) and the names and/or links and/orinformation that are possible, and that may be incorporated into theservice and/or information entry request forms IE₁ . . . IE_(n) (38) atthe user interfaces I₁ . . . I_(n) (14).

C. Typical Completed Service and/or Information Entry Request Forms

FIGS. 11-26 show typical ones of completed service and/or informationentry request forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . .. I_(n) (14).

FIG. 11 shows a typical particular one of the completed service and/orinformation entry request forms IF₁ . . . IF_(n) (230), hereinafterdesignated the completed service and/or information entry request formIF_(n) (230), at a particular one of the user interfaces I₁ . . . I_(n)(14), hereinafter designated the user interface I_(n) (14), having sameand different ones of the typical queries QQ_(n1) . . . QQ_(nm) (53),different ones of the typical server addresses AQ_(n1) . . . AQ_(nm)(54), and the typical optional instructions VJ_(n1) . . . VJ_(nk) (52).Typical same ones of the typical queries QQ_(n1) . . . QQ_(nm) (53), are“Cat”, “Dog”, and “Mouse”, which are different one from the other.

FIG. 12 shows the typical completed service and/or information entryrequest forms IF_(n) (230), at the user interface I_(n) (14), havingsame and different ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), different ones of the typical server addresses AQ_(n1) . . .AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52). Typical same ones of the typical queries QQ_(n1) . . .QQ_(nm) (53) are “Cat”, “Dog”, and “Mouse”, which are different one fromthe other. Typical same ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54) are HotBot®, WebCrawler®, and Dejanews®, which aredifferent one from the other, and which are also different from Yahoo®and LookSmart®. The typical optional instructions VJ_(n1) . . . VJ_(nk)(52) have 5 “URL's per Search Engine”, which instruct the client C_(n)(16) and/or the server PS (18) to return the typical user responseUR_(n) (37), as the typical service and/or information response formIS_(n) (39) at the user interface I_(n) (14) having 5 “URL's per SearchEngine”, rather than 10 “URL's per Search Engine”, as instructed in FIG.11.

FIG. 13 shows the typical completed service and/or information entryrequest forms IF_(n) (230), at the user interface I_(n) (14) having asingle typical one of the typical queries QQ_(n1) . . . QQ_(nm) (53) as“Big Elephants”.

FIGS. 14A, 14B, and 14C show the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14), having same and different ones of the typical queries QQ_(n1) . .. QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) .. . AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), showing “Current Group” as “Group I”, “Group II”, and“Group III”, in FIGS. 14A, 14B, and 14C, respectively. Typical same onesof the typical queries QQ_(n1) . . . QQ_(nm) (53) are “Catcher in theRye”, “Catcher”, “Rye”, “Sports”, and “Rye Bread”, which are differentone from the other. The typical server addresses AQ_(n1) . . . AQ_(nm)(54) are different one from the other. The typical optional instructionsVJ_(n1) . . . VJ_(nk) (52) have a 5 second “Timeout (seconds) per SearchEngine”, rather than a 3 second “Timeout (seconds) per Search Engine” asin FIGS. 11-13. The “Timeout (seconds) per Search Engine” instructs theclient C_(n) (16) and/or the server PS (18) to return the typical userresponse UR_(n) (37), as the typical service and/or information responseform IS_(n) (39) at the user interface I_(n) (14) within a period ofless than the “Timeout (seconds) per Search Engine” specified in thetypical optional instructions VJ_(n1) . . . VJ_(nk) (52). It should benoted that response times of less than one second per search engine aretypical, and response times of substantially less than one second arequite common. However, the “Timeout (seconds) per Search Engine” hasbeen incorporated herein for the user U₁ (12) to specify in the event ofslow ones of the responses R_(n1) . . . R_(nm) (32) from certain ones ofthe servers S₁ . . . S_(z) (20).

FIG. 15 shows the typical completed service and/or information entryrequest forms IF_(n) (230), at the user interface I_(n) (14), havingsame and different ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), different ones of the typical server addresses AQ_(n1) . . .AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52). Typical same ones of the typical queries QQ_(n1) . . .QQ_(nm) (53) are “Charles Dickens”, “A Tale of Two Cities”, and “OliverTwist”, which are different one from the other. All blank entriesbeneath the entry above take on the characteristics of the completedentry above. Therefore, Searches 2, 3, and 4 take on the typical queriesQQ_(n2) . . . QQ_(n4) (53) of “Charles Dickens” of Search 1, above.Likewise, Searches 7, 8, and 9 take on the typical queries QQ_(n7) . . .QQ_(n9) (53) of “Oliver Twist” of Search 6, above. Search 5 takes on thetypical query QQ_(n5) (53) of “A Tale of Two Cities”.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) of FIG. 15have “Separate”, which instruct the client C_(n) (16) and/or the serverPS (18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) in separate groups, i.e., grouped by the typicalserver addresses AQ_(n1) . . . AQ_(nm) (54), rather than interleaved onewith the other, as instructed in FIGS. 11-14.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52)“Interleaved” of FIGS. 11-14 instruct the client C_(n) (16) and/or theserver PS (18) to return the typical user response UR_(n) (37), as thetypical service and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having information and/or services in the responsesR_(n1) . . . R_(nm) (32) to be interleaved one with the other (oralternating one with the other) into the appropriate addressable queryinformation groups GI_(n1) . . . GI_(nz) (63). The labelled individualinformation groups LL_(n11) . . . LL_(nzu) (86) in the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) are alternatinglyinterleaved one with the other and labelled and/or identified andassociated correspondingly with the responses R_(n1) . . . R_(nm) (32)from the servers S₁ . . . S_(z) (20). The “Interleaved” informationand/or services may typically be incorporated into the appropriateaddressable query information groups GI_(n1) . . . GI_(nz) (63) insubstantially the same sequence as the information and/or services arein the responses R_(n1) . . . R_(nm) (32) communicated from the serversS₁ . . . S_(z) (20). However, other sorting/grouping criteria mayoptionally be used, as will be discussed later.

The typical server addresses AQ_(n1) . . . AQ_(nm) (54) are differentone from the other in FIG. 15. The typical optional instructions VJ_(n1). . . VJ_(nk) (52) also instruct the client C_(n) (16) and/or the serverPS (18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having 5 “Searches per Group”, rather than 3“Searches per Group”, as in FIGS. 11-14. The typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52) also instruct the client C_(n)(16) and/or the server PS (18) to return the typical user responseUR_(n) (37), as the typical service and/or information response formIS_(n) (39) at the user interface I_(n) (14) having 8 “URL's per SearchEngine”.

FIG. 16 shows the typical completed service and/or information entryrequest form IF_(n) (230), at the user interface I_(n) (14), having thesame ones of the typical queries QQ_(n1) . . . QQ_(nm) (53), differentones of the typical server addresses AQ_(n1) . . . AQ_(nm) (54), and thetypical optional instructions VJ_(n1) . . . VJ_(nk) (52). The typicaloptional instructions VJ_(n1) . . . VJ_(nk) (52) have “URL Details” as“List”, which instruct the client C_(n) (16) and/or the server PS (18)to return the typical user response UR_(n) (37), as the typical serviceand/or information response form IS_(n) (39) at the user interface I_(n)(14) “List” format rather than “Summary” format, as instructed in FIGS.11-15. The “URL Details” as “Summary” instruct the client C_(n) (16)and/or the server PS (18) to return the typical user response UR_(n)(37) showing descriptions and/or other information and/or services, inaddition to links, in the typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), while “URL Details” as “List”instruct the client C_(n) (16) and/or the server PS (18) to return thetypical user response UR_(n) (37) showing only links in the typical onesof the user responses UR_(n) (37), as the typical service and/orinformation response forms IS_(n) (39) at the user interface I_(n) (14).

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) have 25“URL's per Search Engine”, which instruct the client C_(n) (16) and/orthe server PS (18) to return the typical user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14) having 25 “URL's per Search Engine”. Thetypical optional instructions VJ_(n1) . . . VJ_(nk) (52) also instructthe client C_(n) (16) and/or the server PS (18) to return the typicaluser response UR_(n) (37), as the typical service and/or informationresponse form IS_(n) (39) at the user interface I_(n) (14) having 9“Searches per Group”. The typical optional instructions VJ_(n1) . . .VJ_(nk) (52) also instruct the client C_(n) (16) and/or the server PS(18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) at “Page” 3 of the “Current Group”, rather than“Page” 1 of the “Current Group”, as in FIGS. 11-15. The typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52) also instruct the client C_(n)(16) and/or the server PS (18) to return the typical user responseUR_(n) (37), as the typical service and/or information response formIS_(n) (39) at the user interface I_(n) (14) to use a 2 second “Timeout(seconds) per Search Engine”.

FIG. 17 shows another one of the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14), having the same ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), different ones of the typical server addresses AQ_(n1) . . .AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52). The typical optional instructions VJ_(n1) . . . VJ_(nk)(52) have 18 “URL's per Search Engine”, which instruct the client C_(n)(16) and/or the server PS (18) to return the typical user responseUR_(n) (37), as the typical service and/or information response formIS_(n) (39) at the user interface I_(n) (14) having 18 “URL's per SearchEngine”. The typical optional instructions VJ_(n1) . . . VJ_(nk) (52)also instruct the client C_(n) (16) and/or the server PS (18) to returnthe typical user response UR_(n) (37), as the typical service and/orinformation response form IS_(n) (39) at the user interface I_(n) (14)at “Group” 2, having 4 “Searches per Group”, at “Page” 2 of the “CurrentGroup”, with a 2 second “Timeout (seconds) per Search Engine”, and toreturn the results “Separately”.

FIG. 18 shows another one of the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14), having different ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), different ones of the typical server addresses AQ_(n1) . . .AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52).

FIG. 19 shows another one of the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14), having different ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), as in FIG. 18, the same ones of the typical server addressesAQ_(n1) . . . AQ_(nm) (54), and the typical optional instructionsVJ_(n1) . . . VJ_(nk) (52).

FIG. 20 shows the typical completed service and/or information entryrequest forms IF_(n) (230), at the user interface I_(n) (14) having asingle typical one of the typical queries QQ_(n1) . . . QQ_(nm) (53) as“sports”.

FIG. 21 show another one of the typical completed service and/orinformation entry request forms IF_(n) (230), at the user interfaceI_(n) (14) having a single typical one of the typical queries QQ_(n1) .. . QQ_(nm) (53) as “television”.

FIG. 22 shows another one of the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14), having different ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), i.e., “sports” and “television”, different ones of the typicalserver addresses AQ_(n1) . . . AQ_(nm) (54), and the typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52).

FIG. 23 shows another one of the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14), having the same ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), i.e., “weather”, different ones of the typical server addressesAQ_(n1) . . . AQ_(nm) (54), and the typical optional instructionsVJ_(n1) . . . VJ_(nk) (52).

FIG. 24 shows another one of the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14), having different ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), i.e., “education”, “universities,” and “training”, different onesof the typical server addresses AQ_(n1) . . . AQ_(nm) (54), and thetypical optional instructions VJ_(n1) . . . VJ_(nk) (52).

FIG. 25 shows another one of the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14), having different ones of the typical queries QQ_(n1) . . . QQ_(nm)(53), i.e., “weather”, “climate,” and “training”, different ones of thetypical server addresses AQ_(n1) . . . AQ_(nm) (54), and the typicaloptional instructions VJ_(n1) . . . VJ_(nk) (52).

FIG. 26 shows another one of the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14) having a single typical one of the typical queries QQ_(n1) . . .QQ_(nm) (53) as “weather”.

The typical ones of the completed service and/or information entryrequest forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . . .I_(n) (14) shown in FIG. 11-26 are typical examples of the completedservice and/or information entry request forms IF₁ . . . IF_(n) (230) atthe user interfaces I₁ . . . I_(n) (14), a much larger variety of whichis possible. Typical queries QQ_(n1) . . . QQ_(nm) (53), typical serveraddresses AQ_(n1) . . . AQ_(nm) (54), and typical optional instructionsVJ_(n1) . . . VJ_(nk) (52) in the typical ones of the completed serviceand/or information entry request forms IF₁ . . . IF_(n) (230) at theuser interfaces I₁ . . . I_(n) (14) shown in FIG. 11-26 are typicalexamples for illustrative purposes, and are not intended to limit thesubstantially infinite variety of the queries QQ_(n1) . . . QQ_(nm)(53), the server addresses AQ_(n1) . . . AQ_(nm) (54), and the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) that may be entered into theservice and/or information entry request forms IE₁ . . . IE_(n) (38), toderive the completed service and/or information entry request forms IF₁. . . IF_(n) (230) at the user interfaces I₁ . . . I_(n) (14). Likewise,names and/or links and/or other information are incorporated into thetypical ones of the completed service and/or information entry requestforms IF₁ . . . IF_(n) (230) shown in FIGS. 11-26 for illustrativepurposes, and are not intended to limit the large variety of thecompleted service and/or information entry request forms IF₁ . . .IF_(n) (230) and the names and/or links and/or information that arepossible, and that may be incorporated into the completed service and/orinformation entry request forms IF₁ . . . IF_(n) (230) at the userinterfaces I₁ . . . I_(n) (14).

Any ones of the typical queries QQ_(n1) . . . QQ_(nm) (53), any valueswithin the ranges allowable for the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and any values allowable for the typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52) may be incorporated into thetypical ones of service and/or information entry request forms IE₁ . . .IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14) of FIGS. 5A, 5B,and 6-10, which the users U₁ . . . U_(n) (12) enter to complete thetypical ones of the completed service and/or information entry requestforms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . . . I_(n) (14)of FIGS. 11-26

Any values within the ranges allowable for “Search Engine Results”;“URL's per Search Engine”; “URL Details”; “Timeout (seconds) per SearchEngine”; “Page”; “Searches per Group”; and “Group” may be incorporatedinto the typical ones of service and/or information entry request formsIE₁ . . . IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14) ofFIGS. 5A, 5B, and 6-10, which the users U₁ . . . U_(n) (12) enter tocomplete the typical ones of the completed service and/or informationentry request forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . .. I_(n) (14) of FIGS. 11-26.

The users U₁ . . . U_(n) (12), for example, may enter: the typicalqueries QQ_(n1) . . . QQ_(nm) (53); any values within the rangesallowable for the typical server addresses AQ_(n1) . . . AQ_(nm) (54);and any values allowable for the typical optional instructions VJ_(n1) .. . VJ_(nk) (52), such as, for example, any allowable “Search EngineResults”; “URL's per Search Engine”; “URL Details”; “Timeout (seconds)per Search Engine”; “Page”; “Searches per Group”; and “Group” into thetypical ones of service and/or information entry request forms IE₁ . . .IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14) of FIGS. 5A, 5B,and 6-10, which the users U₁ . . . U_(n) (12) enter to complete thetypical ones of the completed service and/or information entry requestforms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . . . I_(n) (14).The typical ones of the user responses UR₁ . . . UR_(n) (37), as typicalservice and/or information response forms IS₁ . . . IS_(n) (39) at theuser interfaces I₁ . . . I_(n) (14), may then be communicated to thecorresponding ones of the users U₁ . . . U_(n) (12), accordingly. FIGS.27A-52C, inclusive, show typical ones of the user responses UR₁ . . .UR_(n) (37), as the typical service and/or information response formsIS₁ . . . IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14), whichmay be communicated to the corresponding ones of the users U₁ . . .U_(n) (12). The scope of the client-server multitasking system 10 of thepresent invention, the client-server multitasking process 99, and themultitasking process 104, however, is not limited to such values. Use ofsuch values herein is meant only for illustrative purposes, in teachingcertain aspects of the multitasking system 10 of the present invention,the client-server multitasking process 99, and the multitasking process104 by example.

D. Typical Service and/or Information Response Forms

FIGS. 27A-52C, inclusive, show typical ones of the user responses UR₁ .. . UR_(n) (37), as typical service and/or information response formsIS₁ . . . IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14), whichmay be communicated to the corresponding ones of the users U₁ . . .U_(n) (12). A typical particular one of the user responses UR₁ . . .UR_(n) (37), as a particular typical one of the service and/orinformation response forms IS₁ . . . IS_(n) (39) at the particular oneof the user interfaces I₁ . . . I_(n) (14) may hereinafter be designatedas the user response UR_(n) (37), as the typical service and/orinformation response form IS_(n) (39) at the user interface I_(n) (14).

FIGS. 27A-52C, inclusive, also show information in each of the typicalones of the user responses UR_(n) (37), as the typical service and/orinformation response forms IS_(n) (39) at the user interface I_(n) (14),pertaining to the “Current Group”, the “Previous Group”, if appropriate,the “Next Group”, if appropriate, and each “Group” by alphanumerics.FIGS. 27A-52C, inclusive, also show information in each of the typicalones of the user responses UR_(n) (37), as the typical service and/orinformation response forms IS_(n) (39) at the user interfaces I_(n)(14), pertaining to links to additional selections, and/or links toprevious selections, if appropriate, and/or links to future selections,if appropriate, that may be made by pointing to and clicking on theselections to be made.

FIGS. 27A-29C, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIG. 11, havinginformation and/or services from the responses R_(n1) . . . R_(nm) (32)incorporated therein, and incorporated into Group I, Group II, and GroupIII, respectively.

The user U_(n) (12) may optionally select Group II, and/or Group IIIfrom the typical one of the user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) of FIGS. 27A-27C, and/or Group I and/or Group IIIat the user interface I_(n) (14) of FIGS. 28A-28C, and/or Group I,and/or Group TI at the user interface I_(n) (14) of FIGS. 29A-29C. Theuser U_(n) (12) may also select Group I, and/or Group II, and/or GroupIII by entering such into the typical one of the service and/orinformation entry request form IE_(n) (38) at the user interfaces I₁ . .. I_(n) (14), and completing the typical completed service and/orinformation entry request form IF_(n) (230), at the user interface I_(n)(14) with the appropriate selections to be made.

The user U_(n) (12) may also make other selections by entering such intothe typical one of the service and/or information entry request formIE_(n) (38) at the user interfaces I₁ . . . I_(n) (14), and completingthe typical completed service and/or information entry request formIF_(n) (230), at the user interface I_(n) (14) with the appropriateselections to be made, and/or by making such selections through thetypical ones of the user responses UR_(n) (37), as the typical serviceand/or information response forms IS_(n) (39) at the user interfaceI_(n) (14). The user U_(n) (12) may typically make selections bypointing and clicking on the appropriate selections and/or by enteringthe desired information. Such information may be entered by any suitablemeans, including but not limited to mouse, keyboard entry, audibleentry, and/or other suitable means.

FIGS. 27A-29C, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), having the service and/orinformation group G_(n) (35) having the addressable query informationgroups GI_(n1) . . . GI_(nz) (63) therein, the labelled individualinformation groups LL_(n11) . . . LL_(nzu) (86) in the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), the additional requestlinks SL_(n1) . . . SL_(nw) (71), the optional service and/orinformation entry request form IE_(n) (38), and other information and/orservices therein, resulting from the same and different ones of thetypical queries QQ_(n1) . . . QQ_(nm) (53), different ones of thetypical server addresses AQ_(n1) . . . AQ_(nm) (54), and the typicaloptional instructions VJ_(n1) . . . VJ_(nk) (52).

FIGS. 27A-29C, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), resulting from the typical onesof the queries QQ_(n1) . . . QQ_(nm) (53), “Cat”, “Mouse”, and “Dog”,the same ones of the typical queries QQ_(n1) . . . QQ_(n3) (53) andQQ_(n9) (53) being “Cat”, other same ones of the typical queries QQ_(n4)(53) and QQ_(n7) (53) being “Mouse”, but different from “Cat”, and othersame ones of the typical queries QQ_(n5), QQ_(n6) (53), and QQ_(n8) (53)being “Dog”, but different from “Cat” and/or “Mouse”, the typical onesof the queries QQ_(n1) . . . QQ_(nm) (53), “Cat”, “Dog”, and “Mouse”,being different one from the other.

The typical same ones of the typical queries QQ_(n1) . . . QQ_(n3) (53)as “Cat” are incorporated into the addressable query information groupsGI_(n1) (63) of Group I.

The typical one of the queries QQ_(n4) (53) as “Mouse” is incorporatedinto the addressable query information groups GI_(n1) (63) of Group II.The other same ones of the typical queries QQ_(n5) and QQ_(n6) (53) as“Dog are incorporated into the addressable query information groupsGI_(n2) (63) of Group II.

The typical one of the queries QQ_(n7) (53) as “Mouse” is incorporatedinto the addressable query information groups GI_(n1) (63) of Group III.The typical one of the queries QQ_(n8) (53) as “Dog” is incorporatedinto the addressable query information groups GI_(n2) (63) of Group III.The typical one of the queries QQ_(n9) (53) as “Cat” is incorporatedinto the addressable query information groups GI_(n3) (63) of Group III.

FIGS. 27A-29C, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIG. 11 having:“Search Engine Results” as “Interleave”; “URL's per Search Engine” as“10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine”as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as I, II,and III, respectively, for FIGS. 27A-29C, inclusive.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) “URL's perSearch Engine” as “10” instruct the client C_(n) (16) and/or the serverPS (18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having substantially “10” ones of the typicallabelled individual information groups LL_(n11) . . . LL_(nzu) (86) pereach one of the typical server addresses AQ_(n1) . . . AQ_(nm) (54) inthe typical “Current Group”, retrieved from the responses R_(n1) . . .R_(nm) (32). In this case, the typical labelled individual informationgroups LL_(n11) . . . LL_(nzu) (86) may be “Uniform Resource Locators”,or “URL's” and/or other services and/or information associatedtherewith.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) “Searchesper Group” as “3” instruct the client C_(n) (16) and/or the server PS(18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having “3 Searches per Group” for the groupselected, which is designated in the typical optional instructionsVJ_(n1) . . . VJ_(nk) (52) having “Group” as “1”.

“Group I”, which is the “Current Group: I”, has the first three searches(“Searches per Group” designated as “3”), i.e., Search 1, Search 2, andSearch 3, having the typical queries QQ_(n1) . . . QQ_(n3) (53) of“Cat”, “Cat”, and “Cat” and the typical server addresses AQ_(n1) . . .AQ_(n3) (54) of WebCrawler®, Altavista®, and Lycos®.

The “Next Group: II” and/or the “Group: III” may be selected from thetypical user response UR_(n) (37), as the typical service and/orinformation response form IS_(n) (39) at the user interface I_(n) (14).If the “Next Group: II” is selected, then Search 4, Search 5, and Search6, having the typical queries QQ_(n4) . . . QQ_(n6) (53) of “Mouse”,“Dog”, and “Dog” and the typical server addresses AQ_(n4) . . . AQ_(n6)(54) of Infoseek®, Excite®, and Yahoo® are selected and returned as thetypical service and/or information response form IS_(n) (39) at the userinterface I_(n) (14). If the “Group: III” is selected, then Search 7,Search 8, and Search 9, having the typical queries QQ_(n7) . . . QQ_(n9)(53) of “Mouse”, “Dog”, and “Cat” and the typical server addressesAQ_(n7) . . . AQ_(n9) (54) of LookSmart®, HotBot®, and Dejanews®areselected and returned as the typical service and/or information responseform IS_(n) (39) at the user interface I_(n) (14).

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) having“URL's per Search Engine” as “10” and “Searches per Group” as “3”, thenreturns substantially “10 URL's per Search Engine” multiplied by“3Searches per Group”, which is substantially “30 URL's per Group”,and/or other services and/or information associated therewith, returnedin the “Current Group”.

The actual number of the typical “URL's per Group” may vary from thenumber of the “URL's per Search Engine” multiplied by the number of the“Searches per Group”, as duplicate ones of the “URL's” and/or otherservices and/or information associated therewith may typically beoptionally discarded.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) “Page” as“1” instruct the client C_(n) (16) and/or the server PS (18) to returnthe typical user response UR_(n) (37), as the typical service and/orinformation response form IS_(n) (39) at the user interface I_(n) (14)having the first “10 URL's per Search Engine” which is substantially thefirst “30 URL's per Group”, and/or other services and/or informationassociated therewith, in the “Current Group”.

The “Next Page” and/or other pages may be selected, which in thistypical case may be Pages 1-25, from the typical user response UR_(n)(37), as the typical service and/or information response form IS_(n)(39) at the user interface I_(n) (14). If the “Next Page” is selected,then the next “10 URL's per Search Engine” which is substantially thenext “30 URL's per Group”, and/or other services and/or informationassociated therewith, in the “Current Group” are selected and returnedas the typical service and/or information response form IS_(n) (39) atthe user interface I_(n) (14). If, for example, the third “Page’ isselected, then the third “10 URL's per Search Engine” which issubstantially the third “30 URL's per Group”, and/or other servicesand/or information associated therewith, in the “Current Group” areselected and returned as the typical service and/or information responseform IS_(n) (39) at the user interface I_(n) (14).

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) of “SearchEngine Results” as “Interleave” instruct the client C_(n) (16) and/orthe server PS (18) to return the typical user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14) having ones of the typical labelled individualinformation groups LL_(n11) . . . LL_(nzu) (86) and/or other servicesand/or information associated with the typical queries QQ_(n1) . . .QQ_(nm) (53) and the typical server addresses AQ_(n1) . . . AQ_(nm) (54)in the typical “Current Group”, portions of which have been retrievedfrom the responses R_(n1) . . . R_(nm) (32), interleaved one with theother (or alternating one with the other) in the appropriate addressablequery information groups GI_(n1) . . . GI_(nz) (63). The “Interleaved”information and/or services may typically be incorporated into theappropriate addressable query information groups GI_(n1) . . . GI_(nz)(63) in the “Current Group” in substantially the same sequence as theinformation and/or services are in the responses R_(n1) . . . R_(nm)(32) communicated from the servers S₁ . . . S_(z) (20). However, othersorting/grouping criteria may optionally be used, as will be discussedlater. In this case, the typical labelled individual information groupsLL_(n11) . . . LL_(nzu) (86) may be “Uniform Resource Locators”, or“URL's” and/or other services and/or information associated therewith.

“Separate” may be selected from the typical user response UR_(n) (37),as the typical service and/or information response form IS_(n) (39) atthe user interface I_(n) (14), which instructs the client C_(n) (16)and/or the server PS (18) to return the typical user response UR_(n)(37), as the typical service and/or information response form IS_(n)(39) at the user interface I_(n) (14) in “Separate” groups, i.e.,grouped by the typical server addresses AQ_(n1) . . . AQ_(nm) (54)incorporated into the appropriate addressable query information groupsGI_(n1) . . . GI_(nz) (63) in the “Current Group”.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) “URLDetails” as “Summary” instruct the client C_(n) (16) and/or the serverPS (18) to return the typical user response UR_(n) (37) showing thetypical labelled individual information groups LL_(n11) . . . LL_(nzu)(86) showing descriptions and/or other information and/or services, inaddition to links, and/or URL's in the typical ones of the userresponses UR_(n) (37), as the typical service and/or informationresponse forms IS_(n) (39) at the user interface I_(n) (14).

“List” may be selected from the typical user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), which instructs the client C_(n) (16) and/orthe server PS (18) to return the typical user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14) typically showing only links to URL's and/orother links in the typical ones of the user responses UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14).

The “Timeout (seconds) per Search Engine” instructs the client C_(n)(16) and/or the server PS (18) to return the typical user responseUR_(n) (37), as the typical service and/or information response formIS_(n) (39) at the user interface I_(n) (14) within a period of lessthan the “Timeout (seconds) per Search Engine” specified in the typicaloptional instructions VJ_(n1) . . . VJ_(nk) (52). It should be notedthat response times of less than one second per search engine aretypical, and response times of substantially less than one second arequite common. However, the “Timeout (seconds) per Search Engine” hasbeen incorporated herein for the user U₁ (12) to specify in the event ofslow ones of the responses R_(n1) . . . R_(nm) (32) from certain ones ofthe servers S₁ . . . S_(z) (20).

If the time it takes to retrieve information from certain ones of theservers S₁ . . . S_(z) (20) having the typical ones of the queriesQQ_(n1) . . . QQ_(nm) (53) at the typical ones of the server addressesAQ_(n1) . . . AQ_(nm) (54) is greater than the “Timeout” selected, thenthe client C_(n) (16) and/or the server PS (18) typically incorporate amessage and/or messages, such as “No Results Found for ‘Query ‘x” at‘Server Address ‘y” within “z” seconds!” for each of the non-respondingcertain ones of the servers S₁ . . . S_(z) (20), as shown later in FIGS.44A-44C. Information and/or services only from those ones of the serversS₁ . . . S_(z) (20) responding within the “Timeout” period are thenincorporated into the typical ones of the user responses UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14).

FIGS. 30A-32B, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIG. 12, havinginformation and/or services from the responses R_(n1) . . . R_(nm) (32)incorporated therein, and incorporated into Group I, Group II, and GroupIII, respectively.

FIGS. 30A-32B, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), having the service and/orinformation group G_(n) (35) having the addressable query informationgroups GI_(n1) . . . GI_(nz) (63) therein, the labelled individualinformation groups LL_(n11) . . . LL_(nzu) (86) in the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), the additional requestlinks SL_(n1) . . . SL_(nw) (71), the optional service and/orinformation entry request form IE_(n) (38), and other information and/orservices therein, resulting from the same and different ones of thetypical queries QQ_(n1) . . . QQ_(nm) (53), and the same and differentones of the typical server addresses AQ_(n1) . . . AQ_(nm) (54), and thetypical optional instructions VJ_(n1) . . . VJ_(nk) (52), rather thanresults just from different ones of the typical server addresses AQ_(n1). . . AQ_(nm) (54) as in FIGS. 27A-29C, inclusive.

FIGS. 30A-32B, inclusive, show the typical ones of the user responsesUR_(n) (37), as the typical service and/or information response formsIS_(n) (39) at the user interface I_(n) (14), resulting from the typicalones of the queries QQ_(n1) . . . QQ_(nm) (53), “Cat”, “Dog”, and“Mouse”, the same ones of the typical queries QQ_(n1), QQ_(n3) (53), andQQ_(n9) (53) being “Cat”, other same ones of the typical queries QQ_(n2)(53), QQ_(ns) (53), QQ_(n6) (53), and QQ_(n8) (53) being “Dog”, butdifferent from “Cat”, and other same ones of the typical queries QQ_(n4)and QQ_(n7) (53) being “Mouse”, but different from “Cat” and/or “Dog”,the typical ones of the queries QQ_(n1) . . . QQ_(nm) (53), “Cat”,“Dog”, and “Mouse”, being different one from the other.

FIGS. 30A-32B, inclusive, also show the typical ones of the userresponses UR_(n) (37), as the typical service and/or informationresponse forms IS_(n) (39) at the user interface I_(n) (14), resultingfrom the typical ones of the server addresses AQ_(n1) . . . AQ_(nm)(54), HotBot®, WebCrawle®, Yahoo®, LookSmart®, and Dejanews®, the sameones of the typical server addresses AQ_(n1) and AQ_(n2) (54) beingHotBot®, other same ones of the typical server addresses AQ_(n3) . . .AQ_(n5) (54), being WebCrawler®, but different from HotBot®, another oneof the server addresses AQ_(n6) (54), being Yahoo®, but different fromHotBot®, and/or WebCrawler®, another one of the server addresses AQ_(n7)(54), being LookSmart®, but different from HotBot® and/or WebCrawler®and/or Yahoo®, and other same ones of the typical server addressesAQ_(n8) (54) and QQ_(n9) (54) being Dejanews®, but different fromHotBot® and/or WebCrawler® and/or Yahoo® and/or LookSmart®, the typicalones of the server addresses AQ_(n1) . . . AQ_(nm) (54), HotBot®,WebCrawler®, Yahoo®, LookSmart®, and Dejanews®, being different one fromthe other.

The typical same ones of the typical queries QQ_(n1) and QQ_(n3) (53) as“Cat” are incorporated into the addressable query information groupsGI_(n1) (63) of Group I. The typical one of the queries QQ_(n2) (53) as“Cat” is incorporated into the addressable query information groupsGI_(n2) (63) of Group II.

The typical one of the queries QQ_(n4) (53) as “Mouse” is incorporatedinto the addressable query information groups GI_(n1) (63) of Group II.The other same ones of the typical queries QQ_(n5) and QQ_(n6) (53) as“Dog are incorporated into the addressable query information groupsGI_(n2) (63) of Group II.

The typical one of the queries QQ_(n7) (53) as “Mouse” is incorporatedinto the addressable query information groups GI_(n1) (63) of Group III.The typical one of the queries QQ_(n8) (53) as “Dog” is incorporatedinto the addressable query information groups GI_(n2) (63) of Group III.The typical one of the queries QQ_(n9) (53) as “Cat” is incorporatedinto the addressable query information groups GI_(n3) (63) of Group III.

FIGS. 30A-32B, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIG. 12 having:“Search Engine Results” as “Interleave”; “URL's per Search Engine” as“5”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine”as “3”; “Page” as “1”; “Searches per Group as “5”; and “Group” as I, II,and III, respectively, for FIGS. 30A-32B, inclusive.

Now again, FIGS. 30A-32B, inclusive, show the typical ones of the userresponses UR_(n) (37), as the typical service and/or informationresponse forms IS_(n) (39) at the user interface I_(n) (14), resultingfrom the same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), the same and different ones of the typical serveraddresses AQ_(n1) . . . AQ_(nm) (54), and the typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52), but which also result from thetypical optional instructions VJ_(n1) . . . VJ_(nk) (52) having 5 “URL'sper Search Engine”, which instruct the client C_(n) (16) and/or theserver PS (18) to return the typical user response UR_(n) (37), as thetypical service and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having 5 “URL's per Search Engine”, rather than 10“URL's per Search Engine”, as in FIGS. 27A-29C, inclusive.

FIGS. 33A-33C show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 13, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into Group I, having the typical ones of thequeries QQ_(n1) . . . QQ_(nm) (53) as “Big Elephants”. The user U_(n)(12) may optionally select Group II, and/or Group III from the typicalone of the user response UR_(n) (37), as the typical service and/orinformation response form IS_(n) (39) at the user interface I_(n) (14)of FIGS. 33A-33C.

FIGS. 33A-33C show the typical one of the user response UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 13 having: “SearchEngine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URLDetails” as “Summary”; “Timeout (seconds) per Search Engine” as “3”;“Page” as “1”; “Searches per Group as “3”; and “Group” as I. Groups Iand/or II may be selected from the typical one of the user responseUR_(n) (37), as the typical service and/or information response formsIS_(n) (39) at the user interface I_(n) (14) of FIGS. 33A-33C.

FIGS. 34A-36C, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIGS. 14A, 14B,and 14C, respectively, having information and/or services from theresponses R_(n1) . . . R_(nm) (32) incorporated therein, andincorporated into Group I, Group II, and Group III, respectively. FIGS.34A-36C, inclusive, show the results “Interleaved”. Typical ones oflinks, prices, descriptions, savings, and shipping schedules areindicated for products in Group I. The prices may be compared, forexample, one with the other for the same and/or different items,shipping schedules compared, and a decision can be made as to whichitems to order, as a result of the information provided in the typicalone of the user responses UR_(n) (37), as the typical service and/orinformation response forms IS_(n) (39) at the user interface I_(n) (14).Typical similar items may have the same and/or similar titles, such asfor example in book titles, but publication dates, for example, and/oreditions may be the same and/or different, and shipping schedules may bethe same and/or different. Prices, and cost savings may be traded offagainst shipping schedules, packaging (i.e., for example, hardcoverand/or soft cover), author, publisher, for example, and/or other factorsimportant to the user U_(n) (12). The user U_(n) (12) may select theitems and/or items to order from such information that the user U_(n)(12) considers to be important. The user U_(n) (12) may place the orderand/or orders directly through the links and/or URL's in the typicalones of the user responses UR_(n) (37), as the typical service and/orinformation response forms IS_(n) (39) at the user interface I_(n) (14).The user U_(n) (12) may additionally and/or alternatively collect theorder and/or orders in a shopping cart and/or shopping carts associatedwith the typical ones of the user responses UR_(n) (37), as the typicalservice and/or information response forms IS_(n) (39) at the userinterface I_(n) (14), and place the order and/or orders through theclient C_(n) (16) and/or the server PS (18).

Now again, FIGS. 34A-36C, inclusive, show typical ones of the userresponses UR_(n) (37), as the typical service and/or informationresponse forms IS_(n) (39) at the user interface I_(n) (14), having theservice and/or information group G_(n) (35) having the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) therein, the labelledindividual information groups LL_(n11) . . . LL_(nzu) (86) in theaddressable query information groups GI_(n1) . . . GI_(nz) (63), theadditional request links SL_(n1) . . . SL_(nw) (71), the optionalservice and/or information entry request form IE_(n) (38), and otherinformation and/or services therein, resulting from the same anddifferent ones of the typical queries QQ_(n1) . . . QQ_(nm) (53),different ones of the typical server addresses AQ_(n1) . . . AQ_(nm)(54), and the typical optional instructions VJ_(n1) . . . VJ_(nk) (52).Typical same ones of the typical queries QQ_(n1) . . . QQ_(nm) (53) are“Catcher in the Rye”, “Catcher”, “Rye”, “Sports”, and “Rye Bread”, whichare different one from the other. The typical server addresses AQ_(n1) .. . AQ_(nm) (54) are different one from the other.

FIGS. 34A-36C, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIGS. 14A, 14B,and 14C having: “Search Engine Results” as “Interleave”; “URL's perSearch Engine” as “10”; “URL Details” as “Summary”; “Timeout (seconds)per Search Engine” as “5”; “Page” as “1”; “Searches per Group as “3”;and “Group” as I, II, and III, respectively, for FIGS. 34A-36C,inclusive.

Now again, the typical optional instructions VJ_(n1) . . . VJ_(nk) (52)have a 5 second “Timeout (seconds) per Search Engine”, rather than a 3second “Timeout (seconds) per Search Engine” as in FIGS. 27A-33C,inclusive. The “Timeout (seconds) per Search Engine” instructs theclient C_(n) (16) and/or the server PS (18) to return the typical userresponse UR_(n) (37), as the typical service and/or information responseform IS_(n) (39) at the user interface I_(n) (14) within a period ofless than the “Timeout (seconds) per Search Engine” specified in thetypical optional instructions VJ_(n1) . . . VJ_(nk) (52). It should benoted that response times of less than one second per search engine aretypical, and response times of substantially less than one second arequite common. However, the “Timeout (seconds) per Search Engine” hasbeen incorporated herein for the user U₁ (12) to specify in the event ofslow ones of the responses R_(n1) . . . R_(nm) (32) from certain ones ofthe servers S₁ . . . S_(z) (20).

FIGS. 37A-39C, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIG. 15, havinginformation and/or services from the responses R_(n1) . . . R_(nm) (32)incorporated therein, and incorporated into Group I, Group II, and GroupIII, respectively. Links, Prices, descriptions, savings, and shippingschedules are indicated for products in Group I, and Group II. FIGS.38A-38D show the results “Separately” for Group II, and FIGS. 39A-39Cshow the results “Interleaved” for Group II. Links, Prices,descriptions, savings, and shipping schedules are indicated for productsin Groups I and II in FIGS. 37A-39C, inclusive.

FIGS. 37A-39C, inclusive, show typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIG. 15 having:“Search Engine Results” as “Separate”; “URL's per Search Engine” as “8”;“URL Details” as “Summary”; “Timeout (seconds) per Search Engine” as“1”; “Page” as “1”; “Searches per Group as “5”; and “Group” as I, II,and III, respectively for FIGS. 37A-39C, inclusive.

Now again, the typical optional instructions VJ_(n1) . . . VJ_(nk) (52)have “Separate”, which instruct the client C_(n) (16) and/or the serverPS (18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) in separate groups, i.e., grouped by the typicalserver addresses AQ_(n1) . . . AQ_(nm) (54), rather than interleaved onewith the other, as in FIGS. 27A-36C, inclusive.

FIGS. 40A-40M show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 16, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into a single Group.

FIGS. 40A-40M show the typical one of the user response UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 16 having: “SearchEngine Results” as “Interleave”; “URL's per Search Engine” as “25”; “URLDetails” as “List”; “Timeout (seconds) per Search Engine” as “2”; “Page”as “3”; “Searches per Group as “9”; and “Group” as I. Groups I and/or IImay be selected from the typical one of the user response UR_(n) (37),as the typical service and/or information response forms IS_(n) (39) atthe user interface I_(n) (14) of FIGS. 40A-40M.

Now again, the “URL Details” as “Summary” instruct the client C_(n) (16)and/or the server PS (18) to return the typical user response UR_(n)(37) showing descriptions and/or other information and/or services, inaddition to links, in the typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), as in FIGS. 27A-39C, inclusive,while “URL Details” as “List” instruct the client C_(n) (16) and/or theserver PS (18) to return the typical user response UR_(n) (37) showingonly links and/or URL's in the typical ones of the user responses UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), as in FIGS. 40A-40M.

FIGS. 41A-41F show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 17, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into Group II.

FIGS. 41A-41F show the typical one of the user response UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 17 having: “SearchEngine Results” as “Separate”; “URL's per Search Engine” as “18”; “URLDetails” as “Summary”; “Timeout (seconds) per Search Engine” as “1”;“Page” as “2”; “Searches per Group as “4”; and “Group” as “2”. Groups Iand/or III may be selected from the typical one of the user responseUR_(n) (37), as the typical service and/or information response formsIS_(n) (39) at the user interface I_(n) (14) of FIGS. 41A-41F.

FIGS. 42A-42O show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 18, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into a single Group.

FIGS. 42A-42O show the typical one of the user response UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 18 having: “SearchEngine Results” as “Interleave”; “URL's per Search Engine” as “25”; “URLDetails” as “Summary”; “Timeout (seconds) per Search Engine” as “5”;“Page” as “1”; “Searches per Group as “9”; and “Group” as “1”.

FIGS. 43A-43O show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 19, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into a single Group.

FIGS. 43A-43O show the typical one of the user response UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 19 having: “SearchEngine Results” as “Interleave”; “URL's per Search Engine” as “25”; “URLDetails” as “Summary”; “Timeout (seconds) per Search Engine” as “3”;“Page” as “1”; “Searches per Group as “9”; and “Group” as “1”.

FIGS. 44A-44C show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 20, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into Group I. FIGS. 44A-44C also show theresults of a “Timeout” occurring.

FIGS. 44A-44C show the typical one of the user response UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 20 having: “SearchEngine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URLDetails” as “Summary”; “Timeout (seconds) per Search Engine” as “3”;“Page” as “1”; “Searches per Group as “3”; and “Group” as I. Groups Iand/or TI may be selected from the typical one of the user responseUR_(n) (37), as the typical service and/or information response formsIS_(n) (39) at the user interface I_(n) (14) of FIGS. 44A-44C.

FIGS. 45A-45C show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 21, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into Group I.

FIGS. 45A-45C show the typical one of the user response UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 21 having: “SearchEngine Results” as “Interleave”; “URL's per Search Engine” as “10”; “URLDetails” as “Summary”; “Timeout (seconds) per Search Engine” as “3”;“Page” as “1”; “Searches per Group as “3”; and “Group” as I. Groups Iand/or II may be selected from the typical one of the user responseUR_(n) (37), as the typical service and/or information response formsIS_(n) (39) at the user interface I_(n) (14) of FIGS. 45A-45C.

FIGS. 46A-46E show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 22, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into Group I. FIGS. 46A-46E also show thelinks/advertisements/images automatically inserted into the typical oneof the user response UR_(n) (37), as the typical service and/orinformation response form IS_(n) (39) at the user interface I_(n) (14),which may be associated with the typical queries QQ_(n1) . . . QQ_(nm)(53). In the typical case shown in FIGS. 46A-46E,links/advertisements/images associated with the typical queries QQ_(n1). . . QQ_(nm) (53) of “sports” and “television” have been automaticallyinserted into the typical one of the user response UR_(n) (37), as thetypical service and/or information response form IS_(n) (39) at the userinterface I_(n) (14).

FIGS. 46A-46E show the typical one of the user response UR_(n) (37), asthe typical service and/or information response forms IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 22 having: “SearchEngine Results” as “Interleave”; “URL's per Search Engine” as “15”; “URLDetails” as “Summary”; “Timeout (seconds) per Search Engine” as “3”;“Page” as “1”; “Searches per Group as “5”; and “Group” as “1”. NextGroup: II may be selected from the typical one of the user responseUR_(n) (37), as the typical service and/or information response formsIS_(n) (39) at the user interface I_(n) (14) of FIGS. 46A-46E.

FIGS. 47A-47C and 48A-48D show a typical ones of the user responseUR_(n) (37), as the typical service and/or information response formsIS_(n) (39) at the user interface I_(n) (14), with reference to FIG. 23,having information and/or services from the responses R_(n1) . . .R_(nm) (32) incorporated therein, and incorporated into Group I. FIGS.47A-47C and 48A-48D also show the results of a full text search of theoptional database 41 and/or the optional database 42, which may beassociated with the typical queries QQ_(n1) . . . QQ_(nm) (53), andwhich additionally and/or alternatively may function as an internalsearch engine. The full text search results are incorporated from theadditional optional responses RA_(n1) . . . RA_(nm) (40). The results ofthe full text search of the optional database 41 and/or the optionaldatabase 42 may be additionally and/or alternatively automaticallyinserted into the typical one of the user response UR_(n) (37), as thetypical service and/or information response form IS_(n) (39) at the userinterface I_(n) (14), in addition to the typical queries QQ_(n1) . . .QQ_(nm) (53) at the typical ones of the server addresses AQ_(n1) . . .AQ_(nm) (54). In the typical case shown in FIGS. 47A-47C and 48A-48D,full text search results associated with the typical query QQ_(n1) . . .QQ_(nm) (53) of “weather” have been automatically inserted into thetypical ones of the user responses UR_(n) (37), as the typical serviceand/or information response forms IS_(n) (39) at the user interfaceI_(n) (14), in addition to the typical queries QQ_(n1) . . . QQ_(nm)(53) at the typical ones of the server addresses AQ_(n1) . . . AQ_(nm)(54). The typical full text search results start and end with “Hotlist:Weather Science” in FIGS. 47A-47C. The typical full text search resultsstart with “Hotlist: Weather Science” and end with “search for:‘weather’” in FIGS. 48A-48D.

FIGS. 47A-47C and 48A-48D show the typical one of the user responseUR_(n) (37), as the typical service and/or information response formsIS_(n) (39) at the user interface I_(n) (14), with reference to FIG. 23having: “Search Engine Results” as “Interleave”; “URL's per SearchEngine” as “10”; “URL Details” as “Summary”; “Timeout (seconds) perSearch Engine” as “3”; “Page” as “1”; “Searches per Group as “3”; and“Group” as “1”. Next Group: I and/or Group: III may be selected from thetypical one of the user response UR_(n) (37), as the typical serviceand/or information response forms IS_(n) (39) at the user interfaceI_(n) (14) of FIGS. 47A-47C and 48A-48D.

FIGS. 49A-49I show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 24, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into Group I. FIGS. 49A-49I also show thetypical results of the server PS (18) and/or the client C_(n) (16)automatically optionally spidering the sites obtained as a result of thetypical queries QQ_(n1) . . . QQ_(nm) (53) at the typical ones of theserver addresses AQ_(n1) . . . AQ_(nm) (54), and incorporating thespidered results into the optional database 41 and/or the optionaldatabase 42. The spidered results incorporated into the optionaldatabase 41 and/or the optional database 42 may be searched as in FIGS.47A-47C and 48A-48D with reference to FIG. 23 and/or based upon otherones of the typical queries QQ_(n1) . . . QQ_(nm) (53) at the typicalones of the server addresses AQ_(n1) . . . AQ_(nm) (54), and the fulltext search results may be obtained from the additional optionalresponses RA_(n1) . . . RA_(nm) (40).

FIGS. 49A-49I also show the typical one of the user response UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIG. 24 having:“Search Engine Results” as “Interleave”; “URL's per Search Engine” as“10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine”as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as “1”.Next Group: I and/or Group: III may be selected from the typical one ofthe user response UR_(n) (37), as the typical service and/or informationresponse forms IS_(n) (39) at the user interface I_(n) (14) of FIGS.49A-49I.

FIGS. 50A-50K show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 25, having informationand/or services from the responses R_(n1) . . . R_(nm) (32) incorporatedtherein, and incorporated into Group I. FIGS. 50A-50K also show thetypical results of the server PS (18) and/or the client C_(n) (16)semi-automatically optionally spidering the sites obtained as a resultof the typical queries QQ_(n1) . . . QQ_(nm) (53) at the typical ones ofthe server addresses AQ_(n1) . . . AQ_(nm) (54), and incorporating thespidered results into the optional database 41 and/or the optionaldatabase 42. The spidered results incorporated into the optionaldatabase 41 and/or the optional database 42 may also be searched as inFIGS. 47A-47C and 48A-48D with reference to FIG. 23 and/or based uponother ones of the typical queries QQ_(n1) . . . QQ_(nm) (53) at thetypical ones of the server addresses AQ_(n1) . . . AQ_(nm) (54), and thefull text search results may be obtained from the additional optionalresponses RA_(n1) . . . RA_(nm) (40)

The user U_(n) (12) may optionally select those sites to be spidered andincorporated into the optional database 41 and/or the optional database42, as in the typical one of the user response UR_(n) (37), as thetypical service and/or information response form IS_(n) (39) at the userinterface I_(n) (14) in FIGS. 50A-50K. FIGS. 51A-51G show the typicalresults of the server PS (18) and/or the client C_(n) (16) optionallyspidering the sites obtained as a result of the typical queries QQ_(n1). . . QQ_(nm) (53) at the typical ones of the server addresses AQ_(n1) .. . AQ_(nm) (54), and input resulting from user selection of sites to bespidered from FIGS. 50A-50K, and incorporating the spidered results intothe optional database 41 and/or the optional database 42.

The results of the optional spidering typically obtained from thetypical process used with FIGS. 50A-50K and 51A-51G may be substantiallythe same as the typical process used with FIGS. 49A-49I, if all thesites shown in FIGS. 50A-50K are selected for incorporation into thedatabase 41 and/or the optional database 42. The typical process ofFIGS. 49A-49I offers an automatic approach to constructing the optionaldatabase 41 and/or the optional database 42, and the typical process ofFIGS. 50A-50K and 51A-51G offers the flexibility of weeding out and/orselecting sites to be incorporated into the database 41 and/or theoptional database 42.

FIGS. 50A-50K also show the typical one of the user response UR_(n)(37), as the typical service and/or information response forms IS_(n)(39) at the user interface I_(n) (14), with reference to FIG. 25 having:“Search Engine Results” as “Interleave”; “URL's per Search Engine” as“10”; “URL Details” as “Summary”; “Timeout (seconds) per Search Engine”as “3”; “Page” as “1”; “Searches per Group as “3”; and “Group” as “1”.Next Group: I and/or Group: III may be selected from the typical one ofthe user response UR_(n) (37), as the typical service and/or informationresponse forms IS_(n) (39) at the user interface I_(n) (14) of FIGS.50A-50K.

FIGS. 52A-52C show a typical one of the user response UR_(n) (37), asthe typical service and/or information response form IS_(n) (39) at theuser interface I_(n) (14), with reference to FIG. 26, having informationand/or services from the additional optional responses RA_(n1) . . .RA_(nm) (40) FIGS. 52A-52C show the results solely of a full text searchof the optional database 41 and/or the optional database 42, which maybe associated with the typical queries QQ_(n1) . . . QQ_(nm) (53). Thefull text search results are incorporated from the additional optionalresponses RA_(n1) . . . RA_(nm) (40). The typical full text searchresults start with “Hotlist: Weather Science” and end with “High PlainsClimate Center Home Page” in FIGS. 52A-52C.

The typical ones of the user responses UR₁ . . . UR_(n) (37), as typicalservice and/or information response forms IS₁ . . . IS_(n) (39) at theuser interfaces I₁ . . . I_(n) (14) shown in FIGS. 27A-52C, inclusive,are typical examples of the user responses UR₁ . . . UR_(n) (37), astypical service and/or information response forms IS₁ . . . IS_(n) (39)at the user interfaces I₁ . . . I_(n) (14), a much larger variety ofwhich is possible. FIGS. 27A-52C, inclusive, illustrate typical examplesof typical ones of the user responses UR₁ . . . UR_(n) (37), as typicalservice and/or information response forms IS₁ . . . IS_(n) (39) at theuser interfaces I₁ . . . I_(n) (14) to the typical queries QQ_(n1) . . .QQ_(nm) (53), the typical ones of the server addresses AQ_(n1) . . .AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52) having been entered into the typical ones of the completedservice and/or information entry request forms IF₁ . . . IF_(n) (230) atthe user interfaces I₁ . . . I_(n) (14) shown in FIG. 11-26.

The typical examples of the typical ones of the user responses UR₁ . . .UR_(n) (37), as typical service and/or information response forms IS₁ .. . IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14) are forillustrative purposes, and are not intended to limit the substantiallyinfinite variety of the user responses UR₁ . . . UR_(n) (37), as theservice and/or information response forms IS₁ . . . IS_(n) (39) at theuser interfaces I₁ . . . I_(n) (14), the queries QQ_(n1) . . . QQ_(nm)(53), the server addresses AQ_(n1) . . . AQ_(nm) (54), and the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) that may be entered into theservice and/or information entry request forms IE₁ . . . IE_(n) (38), toderive the to the completed service and/or information entry requestforms IF₁ . . . IF_(n) (230), and which result in the user responses UR₁. . . UR_(n) (37), as the service and/or information response forms IS₁. . . IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14). Likewise,names and/or links and/or other information are incorporated into thetypical ones of the user responses UR₁ . . . UR_(n) (37), as the serviceand/or information response forms IS₁ . . . IS_(n) (39) at the userinterfaces I₁ . . . I_(n) (14), shown in FIGS. 27A-52C, inclusive, forillustrative purposes, and are not intended to limit the large varietyof the user responses UR₁ . . . UR_(n) (37), as the service and/orinformation response forms IS₁ . . . IS_(n) (39) at the user interfacesI₁ . . . I_(n) (14), and the names and/or links and/or information thatare possible, and that may be incorporated into the user responses UR₁ .. . UR_(n) (37), as the service and/or information response forms IS₁ .. . IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14).

E. Other Typical Service and/or Information Entry Request Forms, OtherTypical Completed Service and/or Information Entry Request Forms, andOther Typical Service and/or Information Response Forms

FIG. 111 shows another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52). Typical same ones of the typical queries QQ_(n1) . . .QQ_(nm) (53) are “Cat”, “Dog”, and “Mouse”, which are different one fromthe other. Typical same ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54) are Amazon®, Borders®, and BarnesandNoble®, which aredifferent one from the other, and which are also different from Google®.The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) having“URL's per Search Engine” as “10” and “Searches per Group” as “9”, thenreturns substantially “10 URL's per Search Engine” multiplied by“9Searches per Group”, which is substantially “90 URL's per Group”,and/or other services and/or information associated therewith, returnedin the “Current Group”, and Search Engine Results as “Interleaved”. Inthis case, however, order entry boxes 402 are also returned, which allowthe user U₁ (12) to order services, merchandise, information, otheritems, and/or objects through the user interface I₁ (14), as shown inFIGS. 112A-112H. The user U₁ (12) can place orders with sites thatsupport such services and also obtain information on queried subjectsfrom sites that support returning information and/or services.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52)“Interleaved” of FIG. 111 instruct the client C_(n) (16) and/or theserver PS (18) to return the typical user response UR_(n) (37), as thetypical service and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having information and/or services in the responsesR_(n1) . . . R_(nm) (32) to be interleaved one with the other (oralternating one with the other) in the appropriate addressable queryinformation groups GI_(n1) . . . GI_(nz) (63). The labelled individualinformation groups LL_(n11) . . . LL_(nzu) (86) in the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) are alternatinglyinterleaved one with the other and labelled and/or identified andassociated correspondingly with the responses R_(n1) . . . R_(nm) (32)from the servers S₁ . . . S_(z) (20). The “Interleaved” informationand/or services may typically be incorporated into the appropriateaddressable query information groups GI_(n1) . . . GI_(nz) (63) insubstantially the same sequence as the information and/or services inthe responses R_(n1) . . . R_(nm) (32) communicated from the servers S₁. . . S_(z) (20). However, other sorting/grouping criteria mayoptionally be used, as will be discussed.

FIG. 113 shows another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), with other sorting/grouping criteria selected, i.e., withSearch Engine Results as “Combined $[a-z]”.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) “Combined$[a-z]” of FIG. 113 instruct the client C_(n) (16) and/or the server PS(18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having information and/or services in the responsesR_(n1) . . . R_(nm) (32) to be sorted in ascending order firstnumerically, and then alphabetically, in the appropriate addressablequery information groups GI_(n1) . . . GI_(nz) (63). Items having priceswill be sorted numerically by price, with lowest price first. Thelabelled individual information groups LL_(n11) . . . LL_(nzu) (86) inthe addressable query information groups GI_(n1) . . . GI_(nz) (63) aregrouped and sorted in ascending order one with the other and labelledand/or identified and associated correspondingly with the responsesR_(n1) . . . R_(nm) (32) from the servers S₁ . . . S_(z) (20). The“Combined $[a-z]” information and/or services may typically beincorporated into the appropriate addressable query information groupsGI_(n1) . . . GI_(nz) (63) in accordance with the “Combined $[a-z]”optional instructions VJ_(n1) . . . VJ_(nk) (52), and communicated inthe other typical user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), as shown in FIGS. 114A-114H.

FIGS. 114A-114H also depict typical order boxes 402 of a typical orderentry form OF_(n), which is communicated with the typical user responseUR_(n), to enter quantities that the user U_(n) may elect to order, asthe typical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n), which theuser U_(n) may use to enter an order.

FIG. 115 shows another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), with other sorting/grouping criteria selected, i.e., withSearch Engine Results as “Combined $[z-a]”.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) “Combined$[z-a]” of FIG. 115 instruct the client C_(n) (16) and/or the server PS(18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having information and/or services in the responsesR_(n1) . . . R_(nm) (32) to be sorted in descending order firstalphabetically, and then numerically, in the appropriate addressablequery information groups GI_(n1) . . . GI_(nz) (63). Items having priceswill be sorted numerically by price, with highest price first. Thelabelled individual information groups LL_(n11) . . . LL_(nzu) (86) inthe addressable query information groups GI_(n1) . . . GI_(nz) (63) aregrouped and sorted in descending order one with the other and labelledand/or identified and associated correspondingly with the responsesR_(n1) . . . R_(nm) (32) from the servers S₁ . . . S_(z) (20). The“Combined $[z-a]” information and/or services may typically beincorporated into the appropriate addressable query information groupsGI_(n1) . . . GI_(nz) (63) in accordance with the “Combined $[z-a]”optional instructions VJ_(n1) . . . VJ_(nk) (52), and communicated inthe other typical user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), as shown in FIGS. 116A-116H.

FIG. 117 shows another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), with other sorting/grouping criteria selected, i.e., withSearch Engine Results as “Separate”. The typical optional instructionsVJ_(n1) . . . VJ_(nk) (52) of FIG. 117 have “Separate”, which instructthe client C_(n) (16) and/or the server PS (18) to return the typicaluser response UR_(n) (37), as the typical service and/or informationresponse form IS_(n) (39) at the user interface I_(n) (14) in separategroups, i.e., grouped by the typical server addresses AQ_(n1) . . .AQ_(nm) (54), rather than interleaved one with the other, andcommunicated in the other typical user response UR_(n), as the typicalservice and/or information response form IS_(n) at the user interfaceI_(n), which may be communicated to the user U_(n), as shown in FIGS.118A-118H.

FIG. 119 shows another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), with other sorting/grouping criteria selected, i.e., withSearch Engine Results as “Separate $[a-z]”. The typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52) of FIG. 119 have “Separate$[a-z]”, which instruct the client C_(n) (16) and/or the server PS (18)to return the typical user response UR_(n) (37), as the typical serviceand/or information response form IS_(n) (39) at the user interface I_(n)(14) in separate groups, sorted in ascending order first numerically,and then alphabetically, in the appropriate addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), i.e., grouped by thetypical server addresses AQ_(n1) . . . AQ_(nm) (54), and communicated inthe other typical user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), as shown in FIGS. 120A-120H. Itemshaving prices will be sorted numerically by price, with lowest pricefirst within each of the typical server addresses AQ_(n1) . . . AQ_(nm)(54) groups.

FIG. 121 shows another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), with other sorting/grouping criteria selected, i.e., withSearch Engine Results as “Separate $[z-a]”. The typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52) of FIG. 121 have “Separate$[z-a]”, which instruct the client C_(n) (16) and/or the server PS (18)to return the typical user response UR_(n) (37), as the typical serviceand/or information response form IS_(n) (39) at the user interface I_(n)(14) in separate groups, sorted in descending order alphabetically, andthen numerically, in the appropriate addressable query informationgroups GI_(n1) . . . GI_(nz) (63), i.e., grouped by the typical serveraddresses AQ_(n1) . . . AQ_(nm) (54), and communicated in the othertypical user response UR_(n), as the typical service and/or informationresponse form IS_(n) at the user interface I_(n), which may becommunicated to the user U_(n), as shown in FIGS. 122A-122H. Itemshaving prices will be sorted numerically by price, with highest pricefirst within each of the typical server addresses AQ_(n1) . . . AQ_(nm)(54) groups.

FIGS. 123A-123H depict the typical combined user response UR_(n), as thetypical service and/or information response form IS_(n) at the userinterface I_(n), which may be communicated to the user U_(n), and theorder entry form OF_(n), which the user U_(n) may use to enter theorder, of FIGS. 114A-114H, with typical order information enteredtherein.

FIGS. 124A-124B depict a typical preview form of an order OP_(n),resulting from submission of the quantities to be ordered in order boxes402 of the order entry form OF_(n) of FIGS. 114A-114H, of the typicaluser response UR_(n), as the typical service and/or information responseform IS_(n) at the user interface I_(n), with the typical orderinformation entered therein, as shown in FIGS. 123A-123H.

FIGS. 125A-125B depict a typical order placement form OL_(n), having thetypical preview form of the order OP_(n), resulting from submission ofthe order entry form OF_(n), of the typical combined user responseUR_(n), as the typical service and/or information response form IS_(n)at the user interface I_(n), which may be communicated to the userU_(n), and the order entry form OF_(n), which the user U_(n) may use toenter the order, of FIGS. 114A-114H, with the typical order informationentered therein, as shown in FIGS. 123A-123H, or which the user U_(n)may enter through the typical preview form of the order OP_(n) of FIGS.124A-124B.

FIGS. 126A-126B depict a typical completed order placement form OL_(n),having a preview of the order OP_(n), resulting from submission of theorder entry form OF_(n), of the typical combined user response UR_(n),as the typical service and/or information response form IS_(n) at theuser interface I_(n), which may be communicated to the user U_(n), andthe order entry form OF_(n), which the user U_(n) may use to enter theorder, of FIGS. 114A-114H, with the typical order information enteredtherein, as shown in FIGS. 123A-123H, or which the user U_(n) may enterthrough the typical preview form of the order OP_(n) of FIGS. 124A-124B.

FIGS. 127A-127B depict a typical order confirmation OC_(n), resultingfrom submission of the typical completed order placement form OL_(n) ofFIGS. 126A-126B.

The orders are also confirmed automatically by e-mail, with e-mailedconfirmations being sent to the user U_(n) (12), i.e., the buyer,seller, order fulfillment organization, with the total order beingtotaled, portions of the order being segregated and separated one fromthe other, and subtotaled, each segregated and subtotaled portion beingdirected to individual suppliers.

FIGS. 128A-128C depict a typical e-mail order placement EP_(n),resulting from submission of the typical completed order placement formOL_(n) of FIGS. 126A-126B. FIGS. 129A-129C depict a typical e-mailconfirmation of receipt of order EC_(n), resulting from submission ofthe typical completed order placement form OL_(n) of FIGS. 126A-126B.FIGS. 130A-130B depict a typical e-mail order placement EP_(n) of aportion of the order, resulting from submission of the typical completedorder placement form OL_(n) of FIGS. 126A-126B, and FIGS. 131A-131B and132A-132B depict a typical e-mail order placements EP_(n) of otherportions of the order, resulting from submission of the typicalcompleted order placement form OL_(n) of FIGS. 126A-126B.

FIG. 136 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) thereinto, which issubstantially the same as the typical service and/or information entryrequest form IE_(n) at the user interface I_(n) of FIG. 111, except thetypical service and/or information entry request form IE_(n) at the userinterface I_(n) of FIG. 136 is adapted to allow 10 different ones of thetypical queries QQ_(n1) . . . QQ_(nm) (53) and 10 different ones of thetypical server addresses AQ_(n1) . . . AQ_(nm) (54) to be entered,whereas the typical service and/or information entry request form IE_(n)at the user interface I_(n) of FIG. 111 is adapted to allow 9 differentones of the typical queries QQ_(n1) . . . QQ_(nm) (53) and 9 differentones of the typical server addresses AQ_(n1) . . . AQ_(nm) (54) to beentered.

FIG. 137 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) thereinto, which issubstantially the same as the typical service and/or information entryrequest form IE_(n) at the user interface I_(n) of FIG. 136, except thetypical service and/or information entry request form IE_(n) at the userinterface I_(n) of FIG. 137 is adapted to allow the 10 different ones ofthe typical queries QQ_(n1) . . . QQ_(nm) (53) and the 10 different onesof the typical server addresses AQ_(n1) . . . AQ_(nm) (54) to beentered, aligned vertically one with the other in pairs, in two rowspredominantly horizontally adjacent one with the other, whereas thetypical service and/or information entry request form IE_(n) at the userinterface I_(n) of FIG. 136 is adapted to allow the 10 different ones ofthe typical queries QQ_(n1) . . . QQ_(nm) (53) and the 10 different onesof the typical server addresses AQ_(n1) . . . AQ_(nm) (54) to beentered, aligned horizontally one with the other in pairs adjacent onewith the other in vertical rows.

FIG. 138 depicts another typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) thereinto, which issubstantially the same as the typical service and/or information entryrequest form IE_(n) at the user interface I_(n) of FIG. 137, except thetypical service and/or information entry request form IE_(n) at the userinterface I_(n) of FIG. 138 is adapted to allow 12 different ones of thetypical queries QQ_(n1) . . . QQ_(nm) (53) and 12 different ones of thetypical server addresses AQ_(n1) . . . AQ_(nm) (54) to be entered,whereas the typical service and/or information entry request form IE_(n)at the user interface I_(n) of FIG. 138 is adapted to allow 10 differentones of the typical queries QQ_(n1) . . . QQ_(nm) (53) and 10 differentones of the typical server addresses AQ_(n1) . . . AQ_(nm) (54) to beentered.

FIGS. 139-141 depict yet other typical service and/or information entryrequest form IE_(n) at the user interface I_(n), which the user U_(n)may communicate other typical user input UI_(n) thereinto, which aresubstantially the same as the typical service and/or information entryrequest forms IE_(n) at the user interface I_(n) of FIGS. 6, 8, and 10.

Each of the typical service and/or information entry request form IE_(n)at the user interface I_(n), which the user U_(n) may communicate othertypical user input UI_(n) thereinto, of FIGS. 136-141 also have “TopStories”, which are news stories, and are updated intermittently on asubstantially routine basis.

FIG. 142 shows another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), with other sorting/grouping criteria selected, i.e., withSearch Engine Results as “Separate $[a-z]”. The typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52) of FIG. 142 have “Separate$[a-z]”, which instruct the client C_(n) (16) and/or the server PS (18)to return the typical user response UR_(n) (37), as the typical serviceand/or information response form IS_(n) (39) at the user interface I_(n)(14) in separate groups, sorted in ascending order first numerically,and then alphabetically, in the appropriate addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), i.e., grouped by thetypical server addresses AQ_(n1) . . . AQ_(nm) (54), and communicated inthe other typical user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), as shown in FIGS. 143A-143H. Itemshaving prices will be sorted numerically by price, with lowest pricefirst within each of the typical server addresses AQ_(n1) . . . AQ_(nm)(54) groups.

FIG. 144 shows another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), with other sorting/grouping criteria selected, i.e., withSearch Engine Results as “Combined $[a-z]”.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) “Combined$[a-z]” of FIG. 144 instruct the client C_(n) (16) and/or the server PS(18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having information and/or services in the responsesR_(n1) . . . R_(nm) (32) to be sorted in ascending order firstnumerically, and then alphabetically, in the appropriate addressablequery information groups GI_(n1) . . . GI_(nz) (63). Items having priceswill be sorted numerically by price, with lowest price first. Thelabelled individual information groups LL_(n11) . . . LL_(nzu) (86) inthe addressable query information groups GI_(n1) . . . GI_(nz) (63) aregrouped and sorted in ascending order one with the other and labelledand/or identified and associated correspondingly with the responsesR_(n1) . . . R_(nm) (32) from the servers S₁ . . . S_(z) (20). The“Combined $[a-z]” information and/or services may typically beincorporated into the appropriate addressable query information groupsGI_(n1) . . . GI_(nz) (63) in accordance with the “Combined $[a-z]”optional instructions VJ_(n1) . . . VJ_(nk) (52), and communicated inthe other typical user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), as shown in FIGS. 145A-145G.

FIG. 146 shows yet another typical completed service and/or informationentry request form IF_(n) (230), at the user interface I_(n) (14),having same and different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53), different ones of the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and the typical optional instructions VJ_(n1) . . .VJ_(nk) (52), with other sorting/grouping criteria selected, i.e., withSearch Engine Results as “Combined $[a-z]”.

The typical optional instructions VJ_(n1) . . . VJ_(nk) (52) “Combined$[a-z]” of FIG. 146 instruct the client C_(n) (16) and/or the server PS(18) to return the typical user response UR_(n) (37), as the typicalservice and/or information response form IS_(n) (39) at the userinterface I_(n) (14) having information and/or services in the responsesR_(n1) . . . R_(nm) (32) to be sorted in ascending order firstnumerically, and then alphabetically, in the appropriate addressablequery information groups GI_(n1) . . . GI_(nz) (63). Items having priceswill be sorted numerically by price, with lowest price first. Thelabelled individual information groups LL_(n11) . . . LL_(nzu) (86) inthe addressable query information groups GI_(n1) . . . GI_(nz) (63) aregrouped and sorted in ascending order one with the other and labelledand/or identified and associated correspondingly with the responsesR_(n1) . . . R_(nm) (32) from the servers S₁ . . . S_(z) (20). The“Combined $[a-z]” information and/or services may typically beincorporated into the appropriate addressable query information groupsGI_(n1) . . . GI_(nz) (63) in accordance with the “Combined $[a-z]”optional instructions VJ_(n1) . . . VJ_(nk) (52), and communicated inthe other typical user response UR_(n), as the typical service and/orinformation response form IS_(n) at the user interface I_(n), which maybe communicated to the user U_(n), as shown in FIGS. 147A-147G.

Each of the typical service and/or information entry request formsIE_(n) at the user interface I_(n), which the user U_(n) may communicateother typical user input UI_(n) into, of FIGS. 1-147 may also have newsstories, which may be updated intermittently on a substantially routinebasis.

The typical ones of the completed service and/or information entryrequest forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . . .I_(n) (14) shown in certain ones of the FIGS. 1-147 are typical examplesof the completed service and/or information entry request forms IF₁ . .. IF_(n) (230) at the user interfaces I₁ . . . I_(n) (14), a much largervariety of which is possible. Typical queries QQ_(n1) . . . QQ_(nm)(53), typical server addresses AQ_(n1) . . . AQ_(nm) (54), and typicaloptional instructions VJ_(n1) . . . VJ_(nk) (52) in the typical ones ofthe completed service and/or information entry request forms IF₁ . . .IF_(n) (230) at the user interfaces I₁ . . . I_(n) (14) shown in certainones of the FIGS. 1-147 are typical examples for illustrative purposes,and are not intended to limit the substantially infinite variety of thequeries QQ_(n1) . . . QQ_(nm) (53), the server addresses AQ_(n1) . . .AQ_(nm) (54), and the optional instructions VJ_(n1) . . . VJ_(nk) (52)that may be entered into the service and/or information entry requestforms IE₁ . . . IE_(n) (38), to derive the completed service and/orinformation entry request forms IF₁ . . . IF_(n) (230) at the userinterfaces I₁ . . . I_(n) (14). Likewise, names and/or links and/orother information incorporated in the typical ones of the completedservice and/or information entry request forms IF₁ . . . IF_(n) (230)shown in certain ones of the FIGS. 1-147 are for illustrative purposes,and are not intended to limit the large variety of the completed serviceand/or information entry request forms IF₁ . . . IF_(n) (230) and thenames and/or links and/or information that are possible, and that may beincorporated into the completed service and/or information entry requestforms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . . . I_(n) (14).

Any ones of the typical queries QQ_(n1) . . . QQ_(nm) (53), any valueswithin the ranges allowable for the typical server addresses AQ_(n1) . .. AQ_(nm) (54), and any values allowable for the typical optionalinstructions VJ_(n1) . . . VJ_(nk) (52) may be incorporated into thetypical ones of service and/or information entry request forms IE₁ . . .IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14) shown in certainones of the FIGS. 1-147, which the users U₁ . . . U_(n) (12) enter tocomplete the typical ones of the completed service and/or informationentry request forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . .. I_(n) (14) of shown in certain ones of the FIGS. 1-147.

Any values within the ranges allowable for “Search Engine Results”;“URL's per Search Engine”; “URL Details”; “Timeout (seconds) per SearchEngine”; “Page”; “Searches per Group”; and “Group” may be incorporatedinto the typical ones of service and/or information entry request formsIE₁ . . . IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14) shownin certain ones of the FIGS. 1-147, which the users U₁ . . . U_(n) (12)enter to complete the typical ones of the completed service and/orinformation entry request forms IF₁. . . IF_(n) (230) at the userinterfaces I₁ . . . I_(n) (14) shown in certain ones of the FIGS. 1-147.

The users U₁ . . . U_(n) (12), for example, may enter: the typicalqueries QQ_(n1) . . . QQ_(nm) (53); any values within the rangesallowable for the typical server addresses AQ_(n1) . . . AQ_(nm) (54);and any values allowable for the typical optional instructions VJ_(n1) .. . VJ_(nk) (52), such as, for example, any allowable “Search EngineResults”; “URL's per Search Engine”; “URL Details”; “Timeout (seconds)per Search Engine”; “Page”; “Searches per Group”; and “Group” into thetypical ones of service and/or information entry request forms IE₁ . . .IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14 shown in certainones of the FIGS. 1-147, which the users U₁ . . . U_(n) (12) enter tocomplete the typical ones of the completed service and/or informationentry request forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . .. I_(n) (14). The typical ones of the user responses UR₁ . . . UR_(n)(37), as typical service and/or information response forms IS₁ . . .IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14), may then becommunicated to the corresponding ones of the users U₁ . . . U_(n) (12),accordingly. Certain ones of the FIGS. 1-147 show typical ones of theuser responses UR₁ . . . UR_(n) (37), as the typical service and/orinformation response forms IS₁ . . . IS_(n) (39) at the user interfacesI₁ . . . I_(n) (14), which may be communicated to the corresponding onesof the users U₁ . . . U_(n) (12). The scope of the client-servermultitasking system 10 of the present invention, the client-servermultitasking process 99, and the multitasking process 104, however, isnot limited to such values. Use of such values herein is meant only forillustrative purposes, in teaching certain aspects of the multitaskingsystem 10 of the present invention, the client-server multitaskingprocess 99, and the multitasking process 104 by example.

F. Optional Database

The server PS (18) and/or the clients C₁ . . . C_(n) (16) may alsoincorporate corresponding additional optional responses RA₁₁ . . .RA_(nm) (40) into the service and/or information responses IR₁ . . .IR_(n) (34), which may be obtained by accessing optional databases 41and/or 42, shown in FIGS. 53A and 53B, which may be optionally residentwithin the server PS (18) and/or the clients C₁ . . . C_(n) (16),respectively.

The server PS (18) and/or the clients C₁ . . . C_(n) (16) may optionallystore the responses R₁₁ . . . R_(nm) (32) communicated from the serversS₁ . . . S_(z) (20), in accordance with the designation schemecorresponding to the server designations S₁₁ . . . S_(nm) (30) in theoptional databases 41 and/or 42, optionally resident within the serverPS (18) and/or the clients C₁ . . . C_(n) (16), respectively, which maybe optionally retrieved from the optional databases 41 and/or 42, and/oroptionally incorporated into the service and/or information responsesIR₁ . . . IR_(n) (34), and accessed as the additional optional responsesRA₁₁ . . . RA_(nm) (40).

The server PS (18) and/or the clients C₁ . . . C_(n) (16) may optionallycommunicate with the optional servers SO₁ . . . SO_(p) (22), and obtaininformation from each of the optional servers SO₁ . . . SO_(p) (22),which may also be stored in the optional databases 41 and/or 42, whichmay be optionally resident within the server PS (18) and/or the clientsC₁ . . . C_(n) (16), respectively, and which may be optionallyincorporated into the service and/or information responses IR₁ . . .IR_(n) (34), and accessed as the additional optional responses RA₁₁ . .. RA_(nm) (40).

Each of the users U₁ . . . U_(n) (12) may optionally communicatecorresponding additional optional requests q₁₁ . . . q_(np) (44) throughthe corresponding user interfaces I₁ . . . I_(n) (14) and thecorresponding clients C₁ . . . C_(n) (16) to the optional servers SO₁ .. . SO_(p) (22), based upon information in the service and/orinformation responses IR₁ . . . IR_(n) (34) and/or other informationpresented to and/or available and/or known to the users U₁ . . . U_(n)(12) through the corresponding user interfaces I₁ . . . I_(n) (14). Theoptional servers SO₁ . . . SO_(p) (22) reply to the clients C₁ . . .C_(n) (16) with corresponding responses r₁₁ . . . r_(np) (46), which theclients C₁ . . . C_(n) (16) communicate through the corresponding userinterfaces I₁ . . . I_(n) (14) to the corresponding users U₁ . . . U_(n)(12), as shown in FIG. 2 for typical ones of the requests q₁₁ . . .q_(np) (44) and the corresponding responses r₁₁ . . . r_(np) (46).

G. Additional Details

Now, in more detail, the clients C₁ . . . C_(n) (16) and the servers S₁. . . S_(z) (20) reside on the network 24. The users U₁ . . . U_(n) (12)and the corresponding clients C₁ . . . C_(n) (16) communicate one withthe other through the corresponding user interfaces I₁ . . . I_(n) (14).The user U, (12), thus, communicates with the client C₁ (16), one withthe other, through the user interface I₁ (14); the user U₂ (12), thus,communicates with the client C₂ (16), one with the other, through theuser interface I₂ (14); the user U_(n) (12), thus, communicates with theclient C_(n) (16), one with the other, through the user interface I_(n)(14); and so on. Any particular user, designated user U_(n) (12), thus,communicates with corresponding client C_(n) (16), one with the other,through corresponding user interface I_(n) (14), as best shown later inFIGS. 54-56. The user U_(n) (12) may be used to designate any one of theusers U₁ . . . U_(n) (12); the user interface I_(n) (14) may be used todesignate any one of the user interfaces I₁ . . . I_(n) (14); the clientC_(n) (16) may be used to designate any one of the users clients C₁ . .. C_(n) (16); and so on. The client-server multitasking system 10 mayalso have the server PS (18) and the optional servers SO₁ . . . SO_(p)(22) residing on the network 24.

There may be n different or same the service and/or information requestsIQ₁ . . . IQ_(n) (28) present on the network 24 at any time. Each of theservice and/or information requests IQ₁ . . . IQ_(n) (28) may have oneor more of the same and/or different requests Q₁₁ . . . Q_(nm) (29) tobe made of one or more of the same and/or different ones of the serversS₁ . . . S_(z) (20), which are called server designations S₁₁ . . .S_(nm) (30), in accordance with the designation scheme which designatesthe servers S₁ . . . S_(z) (20) to be communicated with corresponding tothe requests Q₁₁ . . . Q_(nm) (29) as the corresponding serverdesignations S₁₁ . . . S_(nm) (30). The service and/or informationrequest IQ_(n) (28) may be used to designate any particular one of theservice and/or information requests IQ₁ . . . IQ_(n) (28). RequestsQ_(n1) . . . Q_(nm) (29) may be used to designate the particularrequests Q₁₁ . . . Q_(nm) (29) associated with and corresponding to theservice and/or information request IQ_(n) (28).

Each of the requests Q₁₁ . . . Q_(1m) from the client C₁ (16) may eachbe different one from the other or the same; each of the requests Q₂₁ .. . Q_(2m) from the client C₂ (16) may each be different one from theother or the same; and each of the requests Q_(n1) . . . Q_(nm) (29)from the client C_(n) (16) may each be different one from the other orthe same, and so on. The requests Q₁₁ . . . Q_(1m) (29), the requestsQ₂₁ . . . Q_(2m) (29), and the requests Q_(n1) . . . Q_(nm) (29), thus,may each be different one from the other, or the same, and so on. Therequests Q₁₁ . . . Q_(nm) (29) from the clients C₁ . . . C_(n) (14),thus, may each be different, one from the other, or the same, and may bemade of the same and/or different ones of the servers S₁ . . . S_(z)(20) at the same time and/or different times, in accordance with thecorresponding server designations S₁₁ . . . S_(nm) (30). There may be mdifferent or same ones of the requests Q_(n1) . . . Q_(nm) (29) from theclient C_(n) (16) at any time, and n×m different and/or same ones of therequests Q₁₁ . . . Q_(nm) (29) of the same and/or different ones of theservers S₁ . . . S_(z) (20) present on the network 24 at any time.

This designation format, in which the first alphanumeric subscript afterthe parameter of interest, for example, as in the parameters Q_(n1) . .. Q_(nm) representing the requests Q_(n1) . . . Q_(nm) (29), representsthe particular parameters corresponding to the user U_(n) (12), and thesecond alphanumeric subscript after the parameter of interest representsthe 1^(st), 2^(nd), 3^(rd), through the mth one of the particularparameters, will be used as a designation scheme throughout. In thisparticular instance, for example, there are then m distinctly the sameand/or different ones of the requests Q_(n1) . . . Q_(nm) (29)associated with the nth user U_(n), which is designated as the userU_(n) (12). There are then the same and/or different m distinctly thesame and/or different server designations S_(n1) . . . S_(nm) (30)associated with the nth user U_(n), which is designated as the userU_(n) (12). The same and/or different requests Q_(n1) . . . Q_(nm) (29),then, may be made of the same and/or different ones of the servers S₁ .. . S_(z) (20), in accordance with the designation scheme correspondingto the corresponding certain ones of the server designations S_(n1) . .. S_(nm) (30), associated with and corresponding to the user U_(n) (12).

Each of the clients C₁ . . . C_(n) (16) may optionally also function asservers. Certain ones of the clients C₁ . . . C_(n) (16) may, therefore,function only as clients, while alternate ones of the clients C₁ . . .C_(n) (16) may function as clients and as servers. Each of the userinterfaces I₁ . . . I_(n) (14) may be integral with the clients C₁ . . .C_(n) (16) or separate from the clients C₁ . . . C_(n) (16). Therefore,certain ones of the user interfaces I₁ . . . I_(n) (14) may be integralwith the clients C₁ . . . C_(n) (16), while yet other ones of the userinterfaces I₁ . . . I_(n) (14) may be separate from the clients C₁ . . .C_(n) (16).

The client-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and the multitasking process 104,the server PS (18) and/or the clients C₁ . . . C_(n) (16) are capable ofretrieving, parsing, processing, formatting, organizing, grouping,sorting, and consolidating services and/or information from the sameand/or different ones of the servers S₁ . . . S_(z) (20), and/or theoptional servers SO₁ . . . SO_(p) (22), and/or the clients C₁ . . .C_(n) (16), having the same and/or different structures, formats,organizations, groupings, and/or data structures, and incorporating theparsed, processed, formatted, organized, grouped, sorted, andconsolidated services and/or information into the user responses UR₁ . .. UR_(n) (37) for delivery to the user interfaces I₁ . . . I_(n) (14)and use by the users U₁ . . . U_(n) (12).

Now, the user interfaces I₁ . . . I_(n) (14) may each be different, onefrom the other, or the same, and may change characteristics over time.Each of the user interfaces I₁ . . . I_(n) (14) may changecharacteristics as a function of time, information, and/or instructions,and/or other means, which may be derived by the users U₁ . . . U_(n)(12) and/or the clients C₁ . . . C_(n) (16) and/or the servers S₁ . . .S_(z) (20), and/or the server PS (18), and/or the optional servers SO₁ .. . SO_(p) (22), and/or derived within the user interfaces I₁ . . .I_(n) (14). The user interface I₁ . . . I_(n) (14) may change state.

The user interface I₁ . . . I_(n) (14) may also change as a function ofoptional timers and/or timed instructions associated with the userinterfaces I₁ . . . I_(n) (14), and/or associated with the clients C₁ .. . C_(n) (16) and/or associated with the servers S₁ . . . S_(z) (20),and/or associated with the server PS (18), and/or associated with theoptional servers SO₁ . . . SO_(p) (22), and/or instructions from theuser U₁ . . . U_(n) (12). Changes in the user interface I_(n) (14) mayappear continuous to the user U_(n) (12), spaced in time, staccato, orstatic depending upon the optional timers and/or the timed instructions.Other conditions may change the user interface I₁ . . . I_(n) (14), aswell.

The user interfaces I₁ . . . I_(n) (14) may be updated continuously,intermittently, manually, randomly, semi-automatically, automatically,repetitively, non-repetitively, singly, plurally, multiplexed, and/or acombination thereof or other suitable manner.

The user interfaces I₁ . . . I_(n) (14) may be visual, such as graphicaluser interfaces, aural, and/or tactile, a combination thereof, and/orother suitable means. The user interfaces I₁ . . . I_(n) (14) may beintegral with the clients C₁ . . . C_(n) (16) or separate.

II. A Particular User, User Interface, and Client on the Network

A. Overview

FIGS. 54-56 show typical particular ones of the users U_(n) (12), thecorresponding ones of the user interfaces U_(n) (12), the correspondingones of the clients C_(n) (16), the server PS (18), the servers S₁ . . .S_(z) (20) designated by the server designations S_(n1) . . . S_(nm)(30) corresponding to the requests Q_(n1) . . . Q_(nm) (29) associatedwith the corresponding ones of the users U_(n) (12), and the optionalservers SO₁ . . . SO_(p) (22) of the client-server multitasking system10 of the present invention, which reside on the network 24. The userU_(n) (12) communicates with the corresponding client C_(n) (16) throughthe corresponding user interface I_(n) (14).

The user U_(n) (12) enters the corresponding user input UI_(n) (25)having one or more same and/or different user requests qu_(n1) . . .qu_(nu) (26) into the user interface I_(n) (14). The user requestsqu_(n1) . . . qu_(nu) (26) are communicated from the user interfaceI_(n) (14) to the client C_(n) (16) within the user service and/orinformation request iq_(n) (27), having the user requests qu_(n1) . . .qu_(nu) (26) and other optional information.

The user interface I_(n) (14) communicates the user service and/orinformation request iq_(n) (27) to the client C_(n) (16), whichoptionally formats the corresponding user service and/or informationrequest iq_(n) (27) into the corresponding service and/or informationrequest IQ_(n) (28), as required. The service and/or information requestIQ_(n) (28) may have one or more the same and/or different requestsQ_(n1) . . . Q_(nm) (29) to be made of the servers S₁ . . . S_(z) (20)designated by the server designations S_(n1) . . . S_(nm) (30) at thesame time.

The client C_(n) (16) may communicate the corresponding service and/orinformation request IQ_(n) (28) to the server PS (18). The server PS(18) parses, processes and/or formats the service and/or informationrequest IQ_(n) (28) received from the client C_(n) (16) into the certainrequests Q_(n1) . . . Q_(nm) (29), and communicates the certain requestsQ_(n1) . . . Q_(nm) (29) to the corresponding certain ones of theservers S₁ . . . S_(z) (20) designated by the server designations S_(n1). . . S_(nm) (30), as shown for typical ones of the certain requestsQ_(n1) . . . Q_(nm) (29) in FIG. 54.

The client C_(n) (16) may alternatively parse, process and/or format theuser service and/or information request iq_(n) (27) into the alternaterequests Q_(n1) . . . Q_(nm) (29), and communicate the alternaterequests Q_(n1) . . . Q_(nm) (29) to the corresponding alternate ones ofthe servers S₁ . . . S_(z) (20) designated by the server designationsS_(n1) . . . S_(nm) (30), as shown for typical alternate ones of therequests Q_(n1) . . . Q_(nm) (29) in FIG. 55.

The client C_(n) (16) may alternatively communicate the correspondingother alternate one of the service and/or information request IQ_(n)(28) to the server PS (18), which parses, processes and/or formats theother alternate one of the service and/or information request IQ_(n)(28) into the other alternate ones of the requests Q_(n1) . . . Q_(nm)(29), and communicates the other alternate ones of the requests Q_(n1) .. . Q_(nm) (29) to the corresponding other alternate ones of the serversS₁₁ . . . S_(nm) (30), and additionally the client C_(n) (16) may alsoparse, process and/or format the user service and/or information requestiq_(n) (27) into yet other alternate ones of the requests Q_(n1) . . .Q_(nm) (29), and communicate the yet other alternate ones of therequests Q_(n1) . . . Q_(nm) (29) to the corresponding yet otheralternate ones of the servers S_(n1) . . . S_(nm) (30), as shown fortypical other alternate ones of the requests Q_(n1) . . . Q_(nm) (29)and typical yet other alternate ones of the requests Q_(n1) . . . Q_(nm)(29) in FIG. 56.

Each of the servers S₁ . . . S_(z) (20) designated by the serverdesignations S_(n1) . . . S_(nm) (30) replies to the server PS (18)and/or the client C_(n) (16), in accordance with the designation schemecorresponding to the corresponding certain ones of the serverdesignations S₁₁ . . . S_(nm) (30), accordingly, and communicates thecorresponding responses R_(n1) . . . R_(nm) (32), associated with therequests Q_(n1) . . . Q_(nm) (29), to the server PS (18) and/or theclient C_(n) (16), accordingly. The server PS (18) and/or the clientC_(n) (16) parse, format, process, group, and organize the responsesR_(n1) . . . R_(nm) (32) into the corresponding service and/orinformation response IR_(n) (34) and/or the user service and/orinformation response ir_(n) (36) having the corresponding parsed,processed, formatted, grouped, and organized service and/or informationgroup G_(n) (35) acceptable to the client C_(n) (16) and the userinterface I_(n) (14). The server PS (18) communicates the service and/orinformation response IR_(n) (34) to the client C_(n) (16), as required.

The client C_(n) (16) formats the service and/or information responsesIR₁ . . . IR_(n) (34) into the corresponding user service and/orinformation response ir_(n) (36), as required, and communicates the userservice and/or information responses ir_(n) (36) to the user interfacesI_(n) (14). The user interface I_(n) (14) incorporates the user serviceand/or information response ir_(n) (36) into the user response UR_(n)(37), which is communicated by the user interfaces I_(n) (14) to theuser U_(n) (12).

The server PS (18) and/or the client C_(n) (16) may optionally alsoincorporate the optional additional corresponding responses RA_(n1) . .. RA_(nm) (40) (shown later in FIGS. 59, 60, 63, and 64) into theservice and/or information response IR_(n) (34), which may be obtainedby accessing the optional databases 41 and/or 42, which may beoptionally resident within the server PS (18) and/or the client C_(n)(16), respectively

The server PS (18) and/or the client C_(n) (16) communicate the serviceand/or information response IR_(n) (34) through the user interface I_(n)(14) to the user U_(n) (12).

The server PS (18) and/or the clients C_(n) (16) may optionally storethe responses R_(n1) . . . R_(nm) (32) communicated from the servers S₁. . . S_(z) (20) designated by the server designations S_(n1) . . .S_(nm) (30) in the optional databases 41 and/or 42, optionally residentwithin the server PS (18) and/or the client C_(n) (16), respectively,which may be optionally retrieved from the optional databases 41 and/or42, and/or optionally incorporated into the service and/or informationresponse IR_(n) (34), and accessed as the additional optional responsesRA_(n1) . . . RA_(nm) (40).

The server PS (18) and/or the client C_(n) (16) may optionallycommunicate with the optional servers SO₁ . . . SO_(p) (22), and obtaininformation from each of the optional servers SO₁ . . . SO_(p) (22),which may also be stored in the optional databases 41 and/or 42, whichmay be optionally resident within the server PS (18) and/or the clientC_(n) (16), respectively, and which may be optionally incorporated intothe service and/or information response IR_(n) (34), and accessed as theadditional optional responses RA_(n1) . . . RA_(nm) (40).

The user U_(n) (12) may optionally communicate the correspondingadditional optional requests q_(n1) . . . q_(np) (44) through the userinterface I_(n) (14) and the client C_(n) (16) to the optional serversSO₁ . . . SO_(p) (22), based upon information in the service and/orinformation response IR_(n) (34) and/or other information presented toand/or available and/or known to the user U_(n) (12) through the userinterface I_(n) (14). The optional servers SO₁ . . . SO_(p) (22) replyto the client C_(n) (16) with the corresponding responses r_(n1) . . .r_(np) (46), which the client C_(n) (16) communicates through the userinterface I_(n) (14) to the user U_(n) (12), as shown in FIGS. 54-56 fortypical ones of the requests q_(n1) . . . q_(np) (44) and thecorresponding responses r_(n1) . . . r_(np) (46).

B. Diagrammatic Regrouping

Now, in more detail, FIG. 57 shows a schematic representation of ones ofthe users U₁ . . . U_(n) (12), the corresponding user interfaces I₁ . .. I_(n) (14), the corresponding clients C₁ . . . C_(n) (16), the serverPS (18), the servers S₁ . . . S_(z) (20), and the optional servers SO₁ .. . SO_(p) (22) of the client-server multitasking system 10 of thepresent invention, constructed in accordance with the present invention,which reside on the network 24, regrouped diagrammatically andalternatively named for illustrative purposes only, to illustrate andvisualize possible typical communication paths. Other than FIG. 57, thenomenclature previously described and utilized will be used throughout.

Now, as shown in FIG. 57, for illustrative purposes only, ones of theclients C₁ . . . C_(n) (16) communicating with the server PS (18), as inFIG. 54, may optionally be designated clients CA₁ . . . CA_(w) (16A),and so on. Ones of the clients C₁ . . . C_(n) (16) communicating withthe servers S₁ . . . S_(z) (20), as in FIG. 55, may optionally bedesignated clients CB₁ . . . CB_(x) (16B), and so on. Ones of theclients C₁ . . . C_(n) (16) communicating with the server PS (18) andwith the servers S₁ . . . S_(z) (20), as in FIG. 56, may optionally bedesignated clients CC₁ . . . CC_(y) (16C), and so on.

The users U₁ . . . U_(n) (12) and the corresponding user interfaces I₁ .. . I_(n) (14) corresponding to the clients C₁ . . . C_(n) (16) may,likewise, optionally be designated in FIG. 57 only: correspondingly tothe clients CA₁ . . . CA_(w) (16A), as users UA₁ . . . UA_(w) (12A) anduser interfaces IA₁ . . . IA_(w) (14A), respectively; correspondingly tothe clients CB₁ . . . CB_(x) (16B), as users UB₁ . . . UB_(x) (12B) anduser interfaces IB₁ . . . IB_(x) (14B), respectively; andcorrespondingly to the clients CC₁ . . . CC_(y) (16C), as users UC₁ . .. UC_(y) (12C) and IC₁ . . . IC_(y) (14C), respectively.

The clients C₁ . . . C_(n) (16) being accounted for, the total of theclients CA₁ . . . CA_(w) (16A), CB₁ . . . CB_(x) (16B), and CC₁ . . .CC_(y) (16C) of FIG. 57 add up to n, where n may be any number greateror equal to one, such that the subscripts w+x+y=n.

II. A Particular Service and/or Information Request and AssociatedService and/or Information Response on the Network

B. The Server PS (18)

FIG. 58 shows a typical particular one of the service and/or informationrequests IQ₁ . . . IQ_(n) (28), designated as the service and/orinformation request IQ_(n) (28), having queries Q_(n1) . . . QQ_(nm)(53), corresponding server addresses AQ_(n1) . . . AQ_(nm) (54), andoptional instructions VJ_(n1) . . . VJ_(nk) (52). The server addressesAQ_(n1) . . . AQ_(nm) (54) and the optional instructions VJ_(n1) . . .VJ_(nk) (52) may be optional, and may depend upon the user interfaceI_(n) (14), and/or other information resident within the server PS (18).

FIG. 59 shows the particular service and/or information request IQ_(n)(28) parsed, processed, and/or formatted into current request groupQA_(nc) (50), request groups QA_(n1) . . . QA_(nz) (51), and optionalinstructions VJ_(n1) . . . VJ_(nk) (52), and utilization of informationtherefrom to make the requests Q_(n1) . . . Q_(nm) (29), obtain theresponses R_(n1) . . . R_(nm) (32), and incorporate informationtherefrom into the particular service and/or information response IR_(n)(34). The current request group QA_(nc) (50) may be any particular onethe request groups QA_(n1) . . . QA_(nz) (51), which may be selected bythe user U_(n) (12).

Upon receipt of the service and/or information requests IQ₁ . . . IQ_(n)(28) at the server PS (18), communicated from the corresponding clientsC₁ . . . C_(n) (16), the server PS (18) parses, processes, and/orformats each of the service and/or information requests IQ₁ . . . IQ_(n)(28) into the corresponding current request groups QA_(1c) . . . QA_(nc)(50) having corresponding queries QQ₁₁ . . . QQ_(nm) (53) andcorresponding server addresses AQ₁₁ . . . AQ_(nm) (54) to openconnections with and make the requests Q₁₁ . . . Q_(nm) (29) of theservers S₁ . . . S_(z) (20), in accordance with the designation schemewhich designates the certain ones of the servers S₁ . . . S_(z) (20) tobe communicated with corresponding to the requests Q₁₁ . . . Q_(nm) (29)as the corresponding server designations S₁₁ . . . S_(nm) (30), shownfor a particular one of the service and/or information requests IQ_(n)(28) in FIG. 59.

The server PS (18) also parses, processes, and/or formats each of theservice and/or information requests IQ₁ . . . IQ_(n) (28) into thecorresponding request groups QA₁₁ . . . QA_(nz) (51) havingcorresponding other queries QQ_(1a) . . . QQ_(nz) (55) and correspondingother server addresses AQ_(1a) . . . AQ_(nz) (56), and the correspondingoptional instructions VJ₁₁₁ . . . VJ_(nk) (52), also shown for aparticular one of the service and/or information requests IQ_(n) (28) inFIG. 59.

The server PS (18) opens connections with and makes the requests Q_(n1). . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20), in accordance withthe designation scheme which designates the certain ones of the serversS₁ . . . S_(z) (20) to be communicated with corresponding to therequests Q_(n1) . . . Q_(nm) (29) as the corresponding serverdesignations S₁₁ . . . S_(nm) (30), shown for the particular one of theservice and/or information requests IQ_(n) (28) corresponding to thecorresponding queries QQ_(n1) . . . QQ_(nm) (53) and the correspondingserver addresses AQ_(n1) . . . AQ_(nm) (54) in the current request groupQA_(nc) (50).

The servers S₁ . . . S_(z) (20) corresponding to the server designationsS₁₁ . . . S_(nm) (30), designated in accordance with the designationscheme which designates the certain ones of the servers S₁ . . . S_(z)(20) to be communicated with corresponding to the requests Q_(n1) . . .Q_(nm) (29) as the corresponding server designations S₁₁ . . . S_(nm)(30), respond to the requests Q_(n1) . . . Q_(nm) (29) with thecorresponding responses R_(n1) . . . R_(nm) (32).

The server PS (18) parses, and/or processes, and/or formats, and/orgroups, and/or organizes each of the responses R_(n1) . . . R_(nm) (32)received from the servers S₁ . . . S_(z) (20) corresponding to theserver designations S_(n1) . . . S_(nm) (30) into correspondingaddressable response information groups RG_(n1) . . . RG_(nm) (57).

The server PS (18) may also make additional optional requests QP_(n1) .. . QP_(nm) (58) of the optional database 41, which may be optionallyresident within the server PS (18), and which may reply with thecorresponding additional optional responses RA_(n1) . . . RA_(nm) (40).The server PS (18) parses, and/or processes, and/or formats, and/orgroups, and/or organizes each of the additional optional responsesRA_(n1) . . . RA_(nm) (40) into corresponding response informationgroups RC_(n1) . . . RC_(nm) (59).

Information from the current request group QA_(nc) (50) having thecorresponding queries QQ_(n1) . . . QQ_(nm) (53) and the correspondingserver addresses AQ_(n1) . . . AQ_(nm) (54) is formulated into acorresponding request pointer/address group QZ_(n) (60) havingpointers/addresses PG_(n1) . . . PG_(nz) (61) associated therewith.

Each of the pointers/addresses PG_(n1) . . . PG_(nz) (61) are directedto point/address corresponding addressable query pointer/address groupsQG_(n1) . . . QG_(nz) (62) associated therewith, which aid in obtaininginformation and/or services from certain ones of addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) to be incorporated intoaddressable query information groups GI_(n1) . . . GI_(nz) (63).

Grouping and/or sorting criteria may be incorporated into the optionalinstructions VJ_(n1) . . . VJ_(nk) (52), which may be entered into theuser interface I_(n) (14) through the user input UI_(n) (25) by the userU_(n) (12). Grouping and/or sorting criteria may additionally and/oralternatively be optionally resident within the server PS (18) and/orthe client C_(n) (16).

The grouping and/or sorting criteria gives the user U_(n) (12) theability to formulate the query information groups GI_(n1) . . . GI_(nz)(63) and the way in which information and/or services from theaddressable response information groups RG_(n1) . . . RG_(nm) (57) ispresented to the user U_(n) (12) through the user interface I_(n) (14).

Each of the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) are associated with the corresponding ones of theaddressable query information groups GI_(n1) . . . GI_(nz) (63). Theaddressable query pointer/address group QG_(n1) (62) is, thus,associated with the addressable query information group GI_(n1) (63);the addressable query pointer/address group QG_(n2) (62) is, thus,associated with the addressable query information group GI_(n2) (63);the addressable query pointer/address group QG_(nz) (62) is, thus,associated with the addressable query information group GI_(nz) (63),and so on.

Each of the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) is formulated based upon the grouping and/or sortingcriteria, which may be incorporated into the optional instructionsVJ_(n1) . . . VJ_(nk) (52), and/or which may additionally and/oralternatively optionally be resident within the server PS (18) and/orthe client C_(n) (16), and/or information within the current requestgroup QA_(nc) (50).

Each of the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) has pointers/addresses PP_(n11) . . . PP_(nmr) (64)directed to address/point information in the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) based upon the groupingand/or sorting criteria, which may be incorporated into the optionalinstructions VJ_(n1) . . . VJ_(nk) (52), and/or which may additionallyand/or alternatively optionally be resident within the server PS (18)and/or the client C_(n) (16), and/or the corresponding queries QQ_(n1) .. . QQ_(nm) (53), and/or the corresponding server addresses AQ_(n1) . .. AQ_(nm) (54) within the current request group QA_(nc) (50).

Information and/or services within each of the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) is addressed with thepointers/addresses PP_(n11) . . . PP_(nmr) (64) from the querypointer/address groups QG_(n1) . . . QG_(nz) (62), and informationand/or services from the addressable response information groups RG_(n1). . . RG_(nm) (57) is incorporated into the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) corresponding to thepointers/addresses PP_(n11) . . . PP_(nmr) (64), which are formulated bythe addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62),in accordance with the grouping and/or sorting criteria.

The corresponding other queries QQ_(na) . . . QQ_(nz) (55) and thecorresponding other server addresses AQ_(na) . . . AQ_(nz) (56) in thecorresponding request groups QA_(n1) . . . QA_(nz) (51) may be used forother ones of the requests Q_(n1) . . . Q_(nm) (29), and may beincorporated into the service and/or information response IR_(n) (34),as part of other information OI_(n) (65), for future use.

Each of the addressable query information groups GI_(n1) . . . GI_(nz)(63) is incorporated into the service and/or information group G_(n)(35). The service and/or information group G_(n) (35) and the otherinformation OI_(n) (65) are incorporated into the service and/orinformation response IR_(n) (34).

The optional instructions VJ_(n1) . . . VJ_(nk) (52) may be used by theserver PS (18) in making the requests Q_(n1) . . . Q_(nm) (29) and/orthe additional optional requests QP_(n1) . . . QP_(nm) (58) of theoptional database 41, and/or in processing, formatting, grouping, andorganizing the responses R_(n1) . . . R_(nm) (32) from the ones of theservers S₁ . . . S_(z) (20) corresponding to the server designationsS_(n1) . . . S_(nm) (30), and/or the additional optional responsesRA_(n1) . . . RA_(nm) (40), into the corresponding service and/orinformation responses IR₁ . . . IR_(n) (34), for grouping and/or sortingcriteria instructions, and/or may be used for other purposes.

FIG. 60 is a schematic representation of the particular service and/orinformation request IQ_(n) (28) parsed, processed, and/or formatted intoa current request group QA_(n) (50), request groups QA_(n1) . . .QA_(nz) (51), and corresponding optional instructions VJ_(n1) . . .VJ_(nk) (52), and utilization of information therefrom to make therequests Qn_(n1) . . . Q_(nm) (29), obtain the responses R_(n1) . . .R_(nm) (32), and incorporate information therefrom into the particularservice and/or information response IR_(n) (34), having simplergrouping/sorting that may be used additionally and/or alternatively tothat of FIG. 59.

The user U_(n) (12) is typically given the option through the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) as to the grouping and/orsorting criteria to be entered into the user interface I_(n) (14)through the user input UI_(n) (25) by the user U_(n) (12). The userU_(n) (12) is typically given the choice as to the grouping and/orsorting criteria to be used as in FIG. 59, and/or the grouping and/orsorting criteria of FIG. 60.

Information from the current request group QA_(nc) (50) having thecorresponding queries QQ_(n1) . . . QQ_(nm) (53) and the correspondingserver addresses AQ_(n1) . . . AQ_(nm) (54) is formulated into acorresponding request pointer/address group QY_(n) (68) havingpointers/addresses PF_(n11) . . . PF_(nmr) (69) associated therewith, asshown in FIG. 60.

Each of the pointers/addresses PF_(n11) . . . PF_(nmr) (69) are directedto point/address the corresponding addressable response informationgroups RG_(n1) . . . RG_(nm) (57), and aid in obtaining informationand/or services from the corresponding addressable response informationgroups RG_(n1) . . . RG_(nm) (57) to be incorporated into theaddressable query information groups GI_(n1) . . . GI_(nz) (63), asshown in FIG. 60.

The grouping and/or sorting criteria allow the user U_(n) (12) to directthe server PS (18) and/or the client C_(n) (16) to sort informationand/or services from the responses R_(n1) . . . R_(nm) (32) and/or theadditional optional responses R_(n1) . . . RA_(nm) (40) from theoptional database 41, such as, for example, by category, query, group,page, order of importance, ascending and/or descending order,alphabetically and/or numerically, value, price, and/or othercharacteristics, and/or to combine and/or interleave the informationand/or services from the responses R_(n1) . . . R_(nm) (32) and/or theadditional optional responses RA_(n1) . . . RA_(nm) (40) one with theother, such as, for example, by order of relevance and/or otherparameters.

FIG. 61 shows the particular service and/or information response IR_(n)(34) having a service and/or information group G_(n) (35), additionalrequest links SL_(n1) . . . SL_(nw) (71), optional order form 72,optional additional advertisements and/or links 73, optional hiddeninformation 74, and the optional service and/or information entryrequest form IE_(n) (38).

The service and/or information group G. (35) has the query informationgroups GI_(n1) . . . GI_(nz) (63), optional database response groups 75,and optional additional advertisements and/or links 76.

The additional request links SL_(n1) . . . SL_(nw) (71) allow the userU_(n) (12) to make additional optional selections, based uponinformation and/or services previously requested by the user U_(n) (12).The additional request links SL_(n1) . . . SL_(nw) (71), which areoptional, may typically have Current Group/Next Group/PreviousGroup/Group Number Links, Server Names in Each Group, Queries in EachGroup, Current Page/Next Page/Previous Page/Page Number Links, SearchDisplay/Link and/or Description Placement/Interleave/Separate, and LinkDescription Options/Summary/Minimize. Other additional ones of theadditional requests links SL_(n1) . . . SL_(nw) (71) and/or combinationsthereof may also be incorporated into the service and/or informationresponse IR_(n) (34).

The optional order form 72 allows direct placement and/or confirmationof orders and/or purchases with the servers S₁ . . . S_(z) (20) and/orthe optional servers SO₁ . . . SO_(p) (22), which reside on the network24. The user U_(n) (12) may enter the order placement into the userinterface I_(n) (14) through the user input UI_(n) (25), and receiveorder confirmation through the user interface I_(n) (14). The clientC_(n) (16) may communicate the order placement from the user interfaceI_(n) (14) to the server PS (18), which may communicate the orderplacement to the servers S₁ . . . S_(z) (20) and/or the optional serversSO₁ . . . SO_(p) (22). The server PS (18) may alternatively and/oradditionally communicate the order confirmation received from theservers S₁ . . . S_(z) (20) and/or the optional servers SO₁ . . . SO_(p)(22) to the client C_(n) (16), which may communicate the orderconfirmation to the user interface I_(n) (14) for presentation to theuser U_(n) (12). The order placement and/or the order confirmation maybe stored within the server PS (18) and/or the client C_(n) (16). Theorder placement and/or the order confirmation is typically secure, andmay be encrypted, and is typically communicated using securecommunications means.

C. Certain Ones of the Clients

Certain ones of the clients C₁ . . . C_(n) (16) may alternatively and/oradditionally make the requests Q₁₁ . . . Q_(nm) (29) of the servers S₁ .. . S_(z) (20), in accordance with the designation scheme whichdesignates the certain ones of the servers S₁ . . . S_(z) (20) to becommunicated with corresponding to the requests Q₁₁ . . . Q_(nm) (29),and formulate the corresponding user service and/or information responseir₁ . . . ir_(n) (36), as previously described.

FIG. 62 shows a typical particular one of the user service and/orinformation requests iq₁ . . . iq_(n) (27), designated as the userservice and/or information request iq_(n) (27), having the queriesQQ_(n1) . . . QQ_(nm) (53), the corresponding server addresses AQ_(n1) .. . AQ_(nm) (54), and the optional instructions VJ_(n1) . . . VJ_(nk)(52). The server addresses AQ_(n1) . . . AQ_(nm) (54) and the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) may be optional, and may dependupon the user interface I_(n) (14), and/or other information residentwithin the client C_(n) (16).

FIG. 63 shows the particular user service and/or information requestiq_(n) (27) parsed, processed, and/or formatted into the current requestgroup QA_(nc) (50), the request groups QA_(n1) . . . QA_(nz) (51), andthe corresponding optional instructions VJ_(n1) . . . VJ_(nk) (52), andutilization of information therefrom to make the requests Q_(n1) . . .Q_(nm) (29), obtain the responses R_(n1) . . . R_(nm) (32), andincorporate information therefrom into the particular user serviceand/or information response ir_(n) (36);

The server PS (18) makes the requests Q₁₁ . . . Q_(nm) (29) of theservers S₁ . . . S_(z) (20), in accordance with the designation schemewhich designates the certain ones of the servers S₁ . . . S_(z) (20) tobe communicated with corresponding to the requests Q₁₁ . . . Q_(nm) (29)as the corresponding server designations S₁₁ . . . S_(nm) (30), as shownin FIG. 59, and certain ones of the clients C₁ . . . C_(n) (16) mayadditionally and/or alternatively make the requests Q₁₁ . . . Q_(nm)(29) of the servers S₁ . . . S_(z) (20), in accordance with thedesignation scheme which designates the certain ones of the servers S₁ .. . S_(z) (20) to be communicated with corresponding to the requests Q₁₁. . . Q_(nm) (29) as the corresponding server designations S₁₁ . . .S_(nm) (30), as shown in FIG. 63.

The clients C_(n) (16) may parse, process, and/or format the userservice and/or information requests iq_(n) (27) and/or organize and/orgroup information and/or services from the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) into the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) substantially the same asthe server PS (18) parses, processes, and/or formats the service and/orinformation requests IQ_(n) (28) from the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) into the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), except that the clientC_(n) (16) may organize the addressable query information groups GI_(n1). . . GI_(nz) (63) into the user service and/or information responseir_(n) (36), as in FIG. 63, and the server PS (18) organizes theaddressable query information groups GI_(n1) . . . GI_(nz) (63) into thecorresponding service and/or information response IR_(n) (34), as inFIG. 59.

Upon receipt of the user service and/or information requests iq₁ . . .iq_(n) (27) at the corresponding clients C₁ . . . C_(n) (16), certainones of the corresponding clients C₁ . . . C_(n) (16) may parse,process, and/or format the corresponding user service and/or informationrequests iq₁ . . . iq_(n) (27) into the corresponding current requestgroups QA_(1c) . . . QA_(nc) (50) having the corresponding queries QQ₁₁. . . QQ_(nm) (53) and the corresponding server addresses AQ₁₁ . . .AQ_(nm) (54) to open connections with and make the requests Q₁₁ . . .Q_(nm) (29) of the servers S₁ . . . S_(z) (20), in accordance with thedesignation scheme which designates the certain ones of the servers S₁ .. . S_(z) (20) to be communicated with corresponding to the requests Q₁₁. . . Q_(nm) (29) as the corresponding server designations S₁₁ . . .S_(nm) (30), shown for a particular one of the user service and/orinformation requests iq₁ . . . iq_(n) (27) in FIG. 63.

The corresponding clients C₁ . . . C_(n) (16) may also parse, process,and/or format the corresponding user service and/or information responseir₁ . . . ir_(n) (36) into the corresponding request groups QA₁₁ . . .QA_(nz) (51) having the corresponding other queries QQ_(1a) . . .QQ_(nz) (55) and the corresponding other server addresses AQ_(1a) . . .AQ_(nz) (56), and the corresponding optional instructions VJ₁₁₁ . . .VJ_(nk) (52), also shown for a particular one of the user service and/orinformation requests iq_(n) (27) in FIG. 63.

A particular one of the corresponding clients C₁ . . . C_(n) (16),designated as the client C_(n) (16), may open connections with and makethe requests Q_(n1) . . . Q_(nm) (29) of the servers S₁ . . . S_(z)(20), in accordance with the designation scheme which designates thecertain ones of the servers S₁ . . . S_(z) (20) to be communicated withcorresponding to the requests Q_(n1) . . . Q_(nm) (29) as thecorresponding server designations S₁₁ . . . S_(nm) (30), shown for theparticular one of the user service and/or information requests iq_(n)(27) corresponding to the corresponding queries QQ_(n1) . . . QQ_(nm)(53) and the corresponding server addresses AQ_(n1) . . . AQ_(nm) (54)in the current request group QA_(nc) (50).

The servers S₁ . . . S_(z) (20) corresponding to the server designationsS₁₁ . . . S_(nm) (30), designated in accordance with the designationscheme which designates the certain ones of the servers S₁ . . . S_(z)(20) to be communicated with corresponding to the requests Q_(n1) . . .Q_(nm) (29) as the corresponding server designations S₁₁ . . . S_(nm)(30), respond to the requests Q_(n1) . . . Q_(nm) (29) with thecorresponding responses R_(n1) . . . R_(nm) (32).

The client C_(n) (16) may parse, and/or process, and/or format, and/orgroup, and/or organize each of the responses R_(n1) . . . R_(nm) (32)received from the servers S₁ . . . S_(z) (20) corresponding to theserver designations S_(n1) . . . S_(nm) (30) into the correspondingaddressable response information groups RG_(n1) . . . RG_(nm) (57).

The client C_(n) (16) may also make additional optional requests QP_(n1). . . QP_(nm) (58) of the optional database 42, which may be optionallyresident within the client C_(n) (16), and which may reply with thecorresponding additional optional responses RA_(n1) . . . RA_(nm) (40).The client C_(n) (16) may parse, and/or process, and/or format, and/orgroup, and/or organize each of the additional optional responses RA_(n1). . . RA_(nm) (40) into the corresponding response information groupsRC_(n1) . . . RC_(nm) (59).

Now again, for the client C_(n) (16), information from the currentrequest group QA_(nc) (50) having the corresponding queries QQ_(n1) . .. QQ_(nm) (53) and the corresponding server addresses AQ_(n1) . . .AQ_(nm) (54) is formulated into the corresponding requestpointer/address group QZ_(n) (60) having the pointers/addresses PG_(n1). . . PG_(nz) (61) associated therewith.

Now again, for the client C_(n) (16), each of the pointers/addressesPG_(n1) . . . PG_(nz) (61) are directed to point/address thecorresponding addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) associated therewith, which aid in obtaining informationand/or services from certain ones of the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) to be incorporated intothe addressable query information groups GI_(n1) . . . GI_(nz) (63).

Yet again, for the client C_(n) (16), grouping and/or sorting criteriamay be incorporated into the optional instructions VJ_(n1) . . . VJ_(nk)(52), which may be entered into the user interface I_(n) (14) throughthe user input UI_(n) (25) by the user U_(n) (12). Grouping and/orsorting criteria may additionally and/or alternatively optionallyresident within the server PS (18) and/or the client C_(n) (16).

Now again, the grouping and/or sorting criteria gives the user U_(n)(12) the ability to formulate the query information groups GI_(n1) . . .GI_(nz) (63) and the way in which information from the addressableresponse information groups RG_(n1) . . . RG_(nm) (57) is presented tothe user U_(n) (12) through the user interface I_(n) (14).

Now again, for the client C_(n) (16), each of the addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62) are associated withthe corresponding ones of the addressable query information groupsGI_(n1) . . . GI_(nz) (63). Each of the addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62) is formulated basedupon the grouping and/or sorting criteria, which may be incorporatedinto the optional instructions VJ_(n1) . . . VJ_(nk) (52), and/or whichmay additionally and/or alternatively optionally be resident within theserver PS (18) and/or the client C_(n) (16), and/or information withinthe current request group QA_(nc) (50).

Now again, for the client C_(n) (16), each of the addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62) has pointers/addressesPP_(n11) . . . PP_(nmr) (64) directed to address/point services and/orinformation in the addressable response information groups RG_(n1) . . .RG_(nm) (57) based upon the grouping and/or sorting criteria, which maybe incorporated into the optional instructions VJ_(n1) . . . VJ_(nk)(52), and/or which may additionally and/or alternatively optionally beresident within the server PS (18) and/or the client C_(n) (16), and/orthe corresponding queries QQ_(n1) . . . QQ_(nm) (53), and/or thecorresponding server addresses AQ_(n1) . . . AQ_(nm) (54) within thecurrent request group QA_(nc) (50).

Yet again, for the client C_(n) (16), the information and/or services ineach of the addressable response information groups RG_(n1) . . .RG_(nm) (57) is addressed with the pointers/addresses PP_(n11) . . .PP_(nmr) (64) from the query pointer/address groups QG_(n1) . . .QG_(nz) (62), and information and/or services from the addressableresponse information groups RG_(n1) . . . RG_(nm) (57) is incorporatedinto the addressable query information groups GI_(n1) . . . GI_(nz) (63)corresponding to the pointers/addresses PP_(n11) . . . PP_(nmr) (64),which are formulated by the addressable query pointer/address groupsQG_(n1) . . . QG_(nz) (62), in accordance with the grouping and/orsorting criteria.

Yet again, for the client C_(n) (16), the corresponding other queriesQQ_(na) . . . QQ_(nz) (55) and the corresponding other server addressesAQ_(na) . . . AQ_(nz) (56) in the corresponding request groups QA_(n1) .. . QA_(nz) (51) may be used for other ones of the requests Q_(n1) . . .Q_(nm) (29), and may be incorporated into the user service and/orinformation response ir_(n) (36), as part of other information OI_(n)(65), for future use.

Now again, for the client C_(n) (16), each of the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) is incorporated into theservice and/or information group G_(n) (35). The service and/orinformation group G_(n) (35) and the other information OI_(n) (65) areincorporated into the service and/or information response IR_(n) (34).

The optional instructions VJ_(n1) . . . VJ_(nk) (52) may be used by theclient C_(n) (16), in making the requests Q_(n1) . . . Q_(nm) (29)and/or the additional optional requests QP_(n1) . . . QP_(nm) (58) ofthe optional database 42, and/or in processing, formatting, grouping,and organizing the responses R_(n1) . . . R_(nm) (32) from the ones ofthe servers S₁ . . . S_(z) (20) corresponding to the server designationsS_(n1) . . . S_(nm) (30), and/or the additional optional responsesRA_(n1) . . . RA_(nm) (40), into user service and/or informationresponse ir_(n) (36), for grouping and/or sorting criteria instructions,and/or may be used for other purposes.

FIG. 64 is a schematic representation of the particular user serviceand/or information request iq_(n) (27) parsed, processed, and/orformatted into the current request group QA_(nc) (50), the requestgroups QA_(n1) . . . QA_(nz) (51), and the corresponding optionalinstructions VJ_(n1) . . . VJ_(nk) (52), and utilization of informationtherefrom to make the requests Q_(n1) . . . Q_(nm) (29), obtain theresponses R_(n1) . . . R_(nm) (32), and incorporate informationtherefrom into the particular user service and/or information responseir_(n) (36), having simpler grouping/sorting that may be usedadditionally and/or alternatively to that of FIG. 63.

The user U_(n) (12) is typically given the option through the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) as to the grouping and/orsorting criteria to be entered into the user interface I_(n) (14)through the user input UI_(n) (25) by the user U_(n) (12). The userU_(n) (12) is typically given the choice as to the grouping and/orsorting criteria of FIG. 63, and/or the grouping and/or sorting criteriaof FIG. 64.

Now again, the client C_(n) (16) may parse, process, and/or format theuser service and/or information requests iq_(n) (27) and/or organizeand/or group information and/or services from the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) into the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) substantially the same asthe server PS (18) parses, processes, and/or formats the service and/orinformation requests IQ_(n) (28) from the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) into the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), except that the clientC_(n) (16) may organize the addressable query information groups GI_(n1). . . GI_(nz) (63) into the user service and/or information responseir_(n) (36), as in FIG. 64, and the server PS (18) organizes theaddressable query information groups GI_(n1) . . . GI_(nz) (63) into thecorresponding service and/or information response IR_(n) (34), as inFIG. 60.

Now again, for the client C_(n) (16), information from the currentrequest group QA_(nc) (50) having the corresponding queries QQ_(n1) . .. QQ_(nm) (53) and the corresponding server addresses AQ_(n1) . . .AQ_(nm) (54) is formulated into the corresponding requestpointer/address group QY_(n) (68) having the pointers/addresses PF_(n11). . . PF_(nmr) (69) associated therewith, as shown in FIG. 64.

Now again, for the client C_(n) (16), each of the pointers/addressesPF_(n11) . . . PF_(nmr) (69) are directed to point/address thecorresponding addressable response information groups RG_(n1) . . .RG_(nm) (57), and aid in obtaining information and/or services from thecorresponding addressable response information groups RG_(n1) . . .RG_(nm) (57) to be incorporated into the addressable query informationgroups GI_(n1) . . . GI_(nz) (63), as shown in FIG. 64.

Again, the grouping and/or sorting criteria allow the user U_(n) (12) todirect the server PS (18) and/or the client C_(n) (16) to sortinformation and/or services from the responses R_(n1) . . . R_(nm) (32)and/or the additional optional responses RA_(n1) . . . RA_(nm) (40) fromthe optional database 41, such as, for example, by category, query,group, page, order of importance, ascending and/or descending order,alphabetically and/or numerically, value, price, and/or othercharacteristics, and/or to combine and/or interleave the informationand/or services from the responses R_(n1) . . . R_(nm) (32) and/or theadditional optional responses RA_(n1) . . . RA_(nm) (40) one with theother, such as, for example, by order of relevance and/or otherparameters.

FIG. 65 shows the particular user service and/or information responseir_(n) (36) having the service and/or information group G_(n) (35), theadditional request links SL_(n1) . . . SL_(nw) (71), the optional orderform 72, the optional additional advertisements and/or links 73, theoptional hidden information 74, and the optional service and/orinformation entry request form IE_(n) (38).

Now again, the service and/or information group G_(n) (35) has the queryinformation groups GI_(n1) . . . GI_(nz) (63), the optional databaseresponse groups 75, and the optional additional advertisements and/orlinks 76.

Yet again, the additional request links SL_(n1) . . . SL_(nw) (71) allowthe user U_(n) (12) to make additional optional selections, based uponinformation and/or services previously requested by the user U_(n) (12).The additional request links SL_(n1) . . . SL_(nw) (71), which areoptional, may typically have Current Group/Next Group/PreviousGroup/Group Number Links, Server Names in Each Group, Queries in EachGroup, Current Page/Next Page/Previous Page/Page Number Links, SearchDisplay/Link and/or Description Placement/Interleave/Separate, and LinkDescription Options/Summary/Minimize. Other additional ones of theadditional request links SL_(n1) . . . SL_(nw) (71) and/or combinationsthereof may also be incorporated into the user service and/orinformation response ir_(n) (36).

Now again, for the client C_(n) (16), the optional order form 72 allowsdirect placement and/or confirmation of orders and/or purchases with theservers S₁ . . . S_(z) (20) and/or the optional servers SO₁ . . . SO_(p)(22), which reside on the network 24. The user U_(n) (12) may enter theorder placement into the user interface I_(n) (14) through the userinput UI_(n) (25), and receive order confirmation through the userinterface I_(n) (14). The client C_(n) (16) may communicate the orderplacement from the user interface I_(n) (14) to the servers S₁ . . .S_(z) (20) and/or the optional servers SO₁ . . . SO_(p) (22), and/orreceive the order confirmation therefrom, and communicate the orderconfirmation from the servers S₁ . . . S_(z) (20) and/or the optionalservers SO₁ . . . SO_(p) (22) to the user interface I_(n) (14) forpresentation to the user U_(n) (12). The order placement and/or theorder confirmation may be stored within the server PS (18) and/or theclient C_(n) (16). The order placement and/or the order confirmation istypically secure, and may be encrypted, and is typically communicatedusing secure communications means.

D. Formulating Query Information Groups

Each of the particular addressable response information groups RG_(n1) .. . RG_(nm) (57), designated as the addressable response informationgroup RG_(nm) (57), has optional addressable individual informationgroups LG_(nm1) . . . LG_(nmr) (80), which may be addressed with thepointers/addresses PP_(nm1) . . . PP_(nmr) (64), as shown in FIGS. 59,63, 66A, 66B, and 66C.

Each of the addressable response information groups RG_(n1) . . .RG_(nm) (57) and each of the optional addressable individual informationgroups LG_(n11) . . . LG_(nmr) (80) in each of the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) may be addressed with thepointers/addresses PP_(n11) . . . PP_(nmr) (64).

Now again, the addressable response information group RG_(nm) (57) hasthe optional addressable individual information groups LG_(nm1) . . .LG_(nmr) (80), which may be addressed with the pointers/addressesPP_(nm1) . . . PP_(nmr) (64). Each of the addressable individualinformation groups LG_(nm1) . . . LG_(nmr) (80) in the addressableresponse information group RG_(nm) (57) may be pointed/addressed by theserver PS (18) and/or the client C_(n) (16) to retrieve all and/or aportion and/or combinations of specific ones of the addressableindividual information groups LG_(nm1) . . . LG_(nmr) (80), from theaddressable response information group RG_(nm) (57), and incorporateinformation and/or services from the addressable individual informationgroups LG_(nm1) . . . LG_(nmr) (80) into certain ones of the addressablequery information groups GI_(n1) . . . GI_(nz) (63), in accordance withthe grouping and/or sorting criteria addressing scheme.

The addressable response information group RG_(nm) (57) having theoptional addressable individual information groups LG_(nm1) . . .LG_(nmr) (80) may have optional addressable pointer/address indicesIN_(nm1) . . . IN_(nmr) (81) correspondingly associated with theoptional addressable individual information groups LG_(nm1) . . .LG_(nmr) (80), which may be addressed/pointed with thepointers/addresses PP_(nm1) . . . PP_(nmr) (64), and which may bepointed/addressed by the server PS (18) and/or the client C_(n) (16) toretrieve all and/or a portion and/or combinations of specific ones ofthe addressable individual information groups LG_(nm1) . . . LG_(nmr)(80), and incorporate information and/or services from the addressableindividual information groups LG_(nm1) . . . LG_(nmr) (80) into thecertain ones of the addressable query information groups GI_(n1) . . .GI_(nz) (63), in accordance with the grouping and/or sorting criteriaaddressing scheme.

FIGS. 66A, 66B, and 66C show the addressable response information groupRG_(nm) (57) having the addressable individual information groupsLG_(nm1) . . . LG_(nmr) (80) showing the optional addressablepointer/address indices IN_(nm1) . . . IN_(nmr) (81) correspondinglyassociated with the optional addressable individual information groupsLG_(nm1) . . . LG_(nmr) (80), which may be addressed/pointed with thepointer/addresses PP_(nm1) (64), PP_(nm2) (64), and PP_(nmr) (64),respectively.

The optional addressable pointer/address index IN_(nm1) (81) iscorrespondingly associated with the optional addressable individualinformation group LG_(nm1) (80). The optional addressablepointer/address index IN_(nm2) (81) is correspondingly associated withthe optional addressable individual information group LG_(nm2) (80), andso on. The optional addressable pointer/address index IN_(nmr) (81) is,thus, correspondingly associated with the optional addressableindividual information group LG_(nm1) (80).

The pointers/addresses PG_(n1) . . . PG_(nz) (61) may be formulated asarrays and/or lists. The pointers/addresses PP_(nm1) . . . PP_(nmr) (64)and/or the pointers/addresses PF_(nm1) . . . PF_(nmr) (69) may beformulated as arrays and/or lists. The arrays may be multidimensionalarrays, and the lists may be lists within lists.

The optional addressable individual information group LG_(nmr) (80) isassociated with and corresponds to a particular one of the addressableindividual information groups LG_(nm1) . . . LG_(nmr) (80) in aparticular one of the addressable response information groups RG_(n1) .. . RG_(nm) (57), designated as the addressable response informationgroup RG_(nm) (57). The first subscript of the optional addressableindividual information groups LG_(nmr) (80) is associated with andcorresponds to the particular service and/or information request IQ_(n)(28) and/or the user service and/or information request iq_(n) (27). Thesecond subscript of the optional addressable individual informationgroups LG_(nmr) (80) is associated with and corresponds to a particularone of “1” through “m” i.e., 1 . . . m, of the addressable responseinformation group RG_(n1) . . . RG_(nm) (57). The third subscript of theoptional addressable individual information groups LG_(nmr) (80) isassociated with and corresponds to a particular one of “1” through “r”i.e., 1 . . . r, of the optional addressable individual informationgroup LG_(nm1) . . . LG_(nmr) (80) within the addressable responseinformation group RG_(nm) (57).

The subscripts of the optional addressable pointer/address indicesIN_(nm1) . . . IN_(nmr) (81) are correspondingly associated with thesubscripts of the corresponding addressable individual informationgroups LG_(nm1) . . . LG_(nmr) (80).

A number and variety of pointing/addressing schemes are possible, whichmay be used for a variety of grouping and sorting criteria schemes andaddressing/pointing schemes.

For example, the pointers/addresses PG_(n1) . . . PG_(nz) (61) of therequest pointer/address group QZ_(n) (60) may be pointed/addressed tocertain ones of the addressable query pointer/address groups QG_(n1) . .. QG_(nz) (62), in accordance with certain grouping and/or sortingcriteria schemes and/or pointing/addressing schemes. Thepointers/addresses PP_(n11) . . . PP_(nmr) (64) of each of thepointed/addressed addressable query pointer/address groups QG_(n11) . .. QG_(nz) (62) may be pointed to the pointer/address indices IN_(n11) .. . IN_(nmr) (81) of the optional addressable individual informationgroups LG_(nm1) . . . LG_(nmr), i.e., 1 . . . r, and thepointers/addresses PP_(n11) . . . PP_(nmr) (64), i.e., 1 . . . m,corresponding to the addressable response information groups RG_(n1) . .. RG_(nm) (57) formulated by the addressable query pointer/addressgroups QG_(n1) . . . QG_(nz () 62) may be pointed to certain ones of theaddressable response information groups RG_(n1) . . . RG_(nm) (57), inaccordance with certain grouping and/or sorting criteria schemes and/oraddressing schemes. This subprocess may be repeated until theinformation and/or services from the optional addressable individualinformation groups LG_(nm1) . . . LG_(nmr) from the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) is incorporated into thecertain ones of the addressable query information groups GI_(n1) . . .GI_(nz) (63), in accordance with the grouping and/or sorting criteriaaddressing scheme, as formulated by the addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62) and the requestpointer/address group QZ_(n) (60).

Alternatively and/or additionally, the pointers/addresses PG_(n1) . . .PG_(nz) (61) of the request pointer/address group QZ_(n) (60) may beincremented through each of the addressable query pointer/address groupsQG_(n1) . . . QG_(nz) (62). The pointers/addresses PP_(n11) . . .PP_(nmr) (64) of each of the pointed/addressed addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62) may be pointed to thepointer/address indices IN_(n11) . . . IN_(nmr) (81) of the optionaladdressable individual information groups LG_(nm1) . . . LG_(nmr), i.e.,1 . . . r, and incremented once, and then the pointers/addressesPP_(n11) . . . PP_(nmr) (64), i.e., 1 . . . m, corresponding to theaddressable response information groups RG_(n1) . . . RG_(nm) (57)formulated by the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) may be incremented through each of the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57). This subprocess may berepeated until the information and/or services from the optionaladdressable individual information groups LG_(nm1) . . . LG_(nmr) fromthe addressable response information groups RG_(n1) . . . RG_(nm) (57)is incorporated into the certain ones of the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), in accordance with thegrouping and/or sorting criteria addressing scheme, and as formulated bythe addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62).

Alternatively and/or additionally, the pointers/addresses PP_(n11) . . .PP_(nmr) (64), i.e., 1 . . . m, may be incremented, corresponding to theaddressable response information groups RG_(n1) . . . RG_(nm) (57)formulated by the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62), and then the pointers/addresses PP_(n11) . . . PP_(nmr)(64), i.e., 1 . . . r, pointing to the pointer/address indices IN_(n11). . . IN_(nmr) (81) of the optional addressable individual informationgroups LG_(nm1) . . . LG_(nmr) may then be incremented. This subprocessmay be repeated until the information and/or services from the optionaladdressable individual information groups LG_(nm1) . . . LG_(nmr) fromthe addressable response information groups RG_(n1) . . . RG_(nm) (57)is incorporated into the certain ones of the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), in accordance with thegrouping and/or sorting criteria addressing scheme, and as formulated bythe addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62).

Alternatively and/or additionally, the pointers/addresses PF_(nm1) . . .PF_(nmr) (69), i.e., 1 . . . m, may be incremented, corresponding to theaddressable response information groups RG_(n1) . . . RG_(nm) (57)formulated by the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62), and then the pointers/addresses PF_(nm1) . . . PF_(nmr)(69), i.e., 1 . . . r, pointing to the pointer/address indices IN_(n11). . . IN_(nmr) (81) of the optional addressable individual informationgroups LG_(nm1) . . . LG_(nmr) may then be incremented. This subprocessmay be repeated until the information and/or services from the optionaladdressable individual information groups LG_(nm1) . . . LG_(nmr) fromthe addressable response information groups RG_(n1) . . . RG_(nm) (57)is incorporated into the certain ones of the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), in accordance with thegrouping and/or sorting criteria addressing scheme, and as formulated bythe addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62).

The typical sorting and/or grouping criteria and the addressing/pointingschemes mentioned immediately above, for example, may group certain onesof the queries QQ_(n1) . . . QQ_(nm) (53) having the same and/orsubstantially the same values into a particular one of the queryinformation groups GI_(n1) . . . GI_(nz) (63), designated as the queryinformation group GI_(nz) (63), as shown in certain ones of FIGS.27A-52C, inclusive.

The grouping and/or sorting criteria and schemes and theaddressing/pointing schemes mentioned herein are but only a smallportion of a much larger variety of grouping and/or sorting criteria andschemes and addressing/pointing schemes and/or combinations thereof thatthe client-server multitasking system 10 of the present invention mayuse and is capable of. The above mentioned examples are included hereinto illustrate but a few examples of the capabilities of theclient-server multitasking system 10 of the present invention.

The addressable individual information groups LG_(nm1) . . . LG_(nmr)(80) are typically parsed, and/or processed, and/or formatted forconsistency of presentation and/or appearance one with the other, as theaddressable individual information groups LG_(nm1) . . . LG_(nmr) (80)are incorporated into the addressable response information groupsRG_(n1) . . . RG_(nm) (57) from the responses R_(n1) . . . R_(nm) (32).

Alternatively and/or additionally the addressable individual informationgroups LG_(nm1) . . . LG_(nmr) (80) may be incorporated into theaddressable response information groups RG_(n1) . . . RG_(nm) (57) fromthe responses R_(n1) . . . R_(nm) (32) in an as-is condition and/or inraw form.

The optional addressable individual information groups LG_(nm1) . . .LG_(nmr) (80) in the addressable response information group RG_(nm)(57), having information and/or services parsed and/or processed, and/orformatted, and/or grouped from the response R_(nm) (32), may becorrespondingly associated with the locations of the information and/orservices in the response R_(nm) (32).

Each of the addressable individual information groups LG_(nm1) . . .LG_(nmr) (80) may have and/or be parsed, and/or processed, and/orformatted, and/or organized, and/or grouped into corresponding optionallinks LD_(nm1) . . . LD_(nmr) (82), and/or corresponding optionaldescriptions DD_(nm1) . . . DD_(nmr) (83), and/or corresponding optionalprices/values PD_(nm1) . . . PD_(nmr) (84), and/or correspondingoptional images ID_(nm1) . . . ID_(nmr) (85), as shown in FIG. 67.

The optional links LD_(mn1) . . . LD_(nmr) (82), the correspondingoptional descriptions DD_(nm1) . . . DD_(nmr) (83), the correspondingoptional prices/values PD_(nm1) . . . PD_(nmr) (84), and thecorresponding optional images ID_(nm1) . . . ID_(nmr) (85),corresponding to the addressable individual information groups LG_(nm1). . . LG_(nmr) (80) are typically associated correspondingly one withthe other.

The optional link LD_(nm1) (82), the corresponding optional descriptionDD_(nm1) (83), the corresponding optional price/value PD_(nm1) (84), andthe corresponding optional image ID_(nm1) (85), corresponding to theoptional individual information group LG_(nm1) (80) are typicallyassociated correspondingly one with the other. The optional linkLD_(nm2) (82), the corresponding optional description DD_(nm2) (83), thecorresponding optional price/value PD_(nm2) (84), and the correspondingoptional image ID_(nm2) (85), corresponding to the addressableindividual information group LG_(nm2) (80) are typically associatedcorrespondingly one with the other, and so on. The optional linkLD_(nmr) (82), the corresponding optional description DD_(nmr) (83), thecorresponding optional price/value PD_(nmr) (84), and the correspondingoptional image ID_(nmr) (85), corresponding to the addressableindividual information group LG_(nmr) (80) are, thus, typicallyassociated correspondingly one with the other.

The addressable individual information groups LG_(nm1) . . . LG_(nmr)(80), which may have the corresponding optional links LD_(nm1) . . .LD_(nmr) (82), and/or the corresponding optional descriptions DD_(nm1) .. . DD_(nmr) (83), and/or the corresponding optional prices/valuesPD_(nm1) . . . PD_(nmr) (84), and/or the corresponding optional imagesID_(nm1) . . . ID_(nmr) (85) are appended with labels/identifiers, asshown in FIG. 68, and incorporated into certain ones of the addressablequery information groups GI_(n1) . . . GI_(nz) (63), depending upon thegrouping and/or sorting criteria. FIG. 69 shows a particular one of theaddressable query information groups GI_(n1) . . . GI_(nz) (63),designated as the query information group GI_(nz) (63).

Now again, the optional addressable individual information groupLG_(nmr) (80) is associated with and corresponds to a particular one ofthe addressable individual information groups LG_(nm1) . . . LG_(nmr)(80) in a particular one of the addressable response information groupsRG_(n1) . . . RG_(nm) (57), designated as the addressable responseinformation group RG_(nm) (57). The first subscript of the optionaladdressable individual information groups LG_(nmr) (80) is associatedwith and corresponds to the particular service and/or informationrequest IQ_(n) (28) and/or the user service and/or information requestiq_(n) (27). The second subscript of the optional addressable individualinformation groups LG_(nmr) (80) is associated with and corresponds to aparticular one of “1” through “m” i.e., 1 . . . m, of the addressableresponse information group RG_(n1) . . . RG_(nm) (57). The thirdsubscript of the optional addressable individual information groupsLG_(nmr) (80) is associated with and corresponds to a particular one of“1” through “r”, i.e., 1 . . . r, of the optional addressable individualinformation group LG_(nm1) . . . LG_(nmr) (80) within the addressableresponse information group RG_(nm) (57).

FIG. 68 shows a labelled individual information group LL_(nzu) (86)associated with a particular one of the addressable query informationgroups GI_(n1) . . . GI_(nz) (63), designated as the addressable queryinformation group GI_(nz) (63), having optional group identifier GL_(nc)(87), optional query link identifier LN_(ncu) (88), optional resourcelocation identifier SU_(nw) (89), optional server and/or queryidentifier SI_(nm) (90), and/or optional server link identifier LX_(nmr)(91) appended to the addressable individual information group LG_(nmr)(80).

The first alphanumeric subscript of the labelled individual informationgroup LL_(nzu) (86) is associated with and corresponds to the serviceand/or information response IR_(n) (34) and/or the user service and/orinformation response ir_(n) (36). The second alphanumeric subscript ofthe labelled individual information group LL_(nzu) (86) is associatedwith and corresponds to a particular one of “1” through “z”, i.e., 1 . .. z, of the addressable query information groups GI_(n1) . . . GI_(nz)(63), designated as the addressable query information group GI_(nz)(63), which the labelled individual information group LL_(nzu) (86) isincorporated in. The third alphanumeric subscript of the labelledindividual information group LL_(nzu) (86) is associated with andcorresponds to a particular one of “1” through “u”, i.e., 1 . . . u, oflabelled individual information groups LL_(nz1) . . . LL_(nzu) (86)within the addressable query information group GI_(nz) (63).

The optional group identifier GL_(nc) (87) labels and/or identifies thecurrent request group QA_(nc) (50). The optional group identifierGL_(nc) (87) is associated with and corresponds to the current requestgroup QA_(nc) (50), which may be any particular one the request groupsQA_(n1) . . . QA_(nz) (51) selected by the user U_(n) (12). The firstalphanumeric subscript of the optional group identifier GL_(nc) (87) isassociated with and corresponds to the service and/or informationresponse IR_(n) (34) and/or the user service and/or information responseir_(n) (36). The second subscript of the optional group identifierGL_(nc) (87) is associated with and corresponds to the particular one ofthe request groups QA_(n1) . . . QA_(nz) (51) selected by the user U_(n)(12) as the current request group QA_(nc) (50).

The optional query link identifier LN_(ncu) (88) is also associated withand corresponds to the current request group QA_(nc) (50). The optionalquery link identifier LN_(ncu) (88) labels and/or identifies thelabelled individual information group LL_(ncu) (86). The firstalphanumeric subscript of the optional query link identifier LNncu (88)is associated with and corresponds to the service and/or informationresponse IR_(n) (34) and/or the user service and/or information responseir_(n) (36). The second subscript of the optional query link identifierLN_(ncu) (88) is also associated with and corresponds to the particularone of the request groups QA_(n1) . . . QA_(nz) (51) selected by theuser U_(n) (12) as the current request group QA_(nc) (50). The thirdalphanumeric subscript of the optional query link identifier LN_(ncu)(88) is associated with and corresponds to a particular one of “1”through Iu”, i. e., 1 . . . u, of the labelled individual informationgroups LL_(nz1) . . . LL_(nzu) (86) in the addressable query informationgroup GI_(nz) (63).

The optional resource location identifier SU_(nw) (89) labels and/oridentifies resource locations of information and/or services associatedwith and corresponding to the optional addressable individualinformation group LG_(nmr) (80) in the labelled individual informationgroup LL_(nzu) (86). The optional resource location identifier SU_(nw)(89) indicates and is associated with and corresponds to resourcelocations of information and/or services associated with certain ones ofthe optional servers SO₁ . . . SO_(p) (22) and/or certain ones of theservers S₁ . . . S_(z) (20). The optional resource location identifierSU_(nw) (89) may be obtained from certain information in the optionaladdressable individual information group LG_(nmr) (80). The firstalphanumeric subscript of the optional resource location identifierSU_(nw) (89) is associated with and corresponds to the service and/orinformation response IR_(n) (34) and/or the user service and/orinformation response ir_(n) (36). The second alphanumeric subscript ofthe optional resource location identifier SU_(nw) (89) is associatedwith and corresponds to a particular one of “1” through “w”, i.e., 1 . .. w, of the optional resource location identifiers SU_(n1) . . . SU_(nw)(89) in the labelled individual information group LL_(nzu) (86).

The optional server and/or query identifier SI_(nm) (90) labels and/oridentifies the query QQ_(nm) (53) and/or the corresponding serveraddress AQ_(nm) (54) associated with and corresponding to the optionaladdressable individual information group LG_(nmr) (80) in thecorresponding labelled individual information group LL_(nzu) (86) of thecurrent request group QA_(nc) (50). The first alphanumeric subscript ofthe optional server and/or query identifier SI_(nm) (90) is associatedwith and corresponds to the service and/or information response IR_(n)(34) and/or the user service and/or information response ir_(n) (36).The second alphanumeric subscript of the optional server and/or queryidentifier SI_(nm) (90) is associated with and corresponds to aparticular one of “1” through “m”, i.e., 1 . . . m, of the optionalserver and/or query identifiers SI_(n1) . . . SI_(nm) (90), which may becorrespondingly associated with the corresponding ones of the queriesQQ_(n1) . . . QQ_(nm) (53) and/or the corresponding ones of the serveraddresses AQ_(n1) . . . AQ_(nm) (54).

The optional server link identifier LX_(nmr) (91) labels and/oridentifies the location of the optional addressable individualinformation group LG_(nmr) (80) in the corresponding addressableresponse information groups RG_(nm) (57). The first alphanumericsubscript of the optional server link identifier LX_(nmr) (91) isassociated with and corresponds to the service and/or informationresponse IR_(n) (34) and/or the user service and/or information responseir_(n) (36). The second alphanumeric subscript of the optional serverlink identifier LX_(nmr) (91) is associated with and corresponds to theaddressable response information group RG_(nm) (57). The thirdalphanumeric subscript of the optional server link identifier LX_(nmr)(91) is associated with and corresponds to a particular one of “1”through “r”, i.e., 1 . . . r, of the optional server link identifiersLX_(nm1) . . . LX_(nmr) (91), which may be correspondingly associatedwith the locations of certain ones of the optional addressableindividual information group LG_(nm1) . . . LG_(nmr) (80) in theaddressable response information groups RG_(nm) (57). The certain onesof the optional addressable individual information groups LG_(nm1) . . .LG_(nmr) (80) in the addressable response information group RG_(nm)(57), having information and/or services parsed and/or processed, and/orformatted, and/or grouped from the response R_(nm) (32), which arelabelled and/or identified with the optional server link identifiersLX_(nm1) . . . LX_(nmr) (91), are correspondingly associated with thelocations of the information and/or services in the response R_(nm)(32). The optional server link identifiers LX_(nm1) . . . LX_(nmr) (91),thus, identify and/or label the location of services and/or informationin the response R_(nm) (32).

FIG. 69 shows the addressable query information group GI_(nz) (63)having the labelled individual information groups LL_(nz1) . . .LL_(nzu) (86), optional database labelled individual information groupsRL_(nz1) . . . RL_(nzx) (92), optional query description QT_(nz) (93),optional server descriptions and/or links ST_(nz1) . . . ST_(nzf) (94),and optional advertisements and/or links LT_(nz1) . . . LT_(nzt) (95).The first and second subscripts of the optional database labelledindividual information groups RL_(nz1) . . . RL_(nzx) (92), the optionalquery description QT_(nz) (93), the optional server descriptions and/orlinks ST_(nz1) . . . ST_(nzf) (94), and the optional advertisementsand/or links ST_(nz1) . . . ST_(nzf) (95) are associated with andcorrespond to the addressable query information group GI_(n), (63). Thethird subscripts of the optional database labelled individualinformation groups RL_(nz1) . . . RL_(nzx) (92), the optional serverdescriptions and/or links ST_(nz1) . . . ST_(nzf) (94), and the optionaladvertisements and/or links ST_(nz1) . . . ST_(nzt) (95) are associatedwith and correspond to ones of the optional database labelled individualinformation groups RL_(nz1) . . . RL_(nzx) (92), the optional serverdescriptions and/or links ST_(nz1) . . . ST_(nzf) (94), and the optionaladvertisements and/or links LT_(nz1) . . . LT_(nzt) (95), respectively.

IV Process

FIG. 70 shows steps of a client-server multitasking process 99 of thepresent invention. The client-server multitasking process 99 is shownfor the client-server multitasking system 10 for a particular one of theusers U . . . U_(n) (12), designated as the user U_(n) (12), thecorresponding particular one of the user interfaces I . . . I_(n) (14),designated as the user interface I_(n) (14), the correspondingparticular one of the clients C . . . C_(n) (16), designated as theclient C_(n) (16), the server PS (18), the servers S₁ . . . S_(z) (20),and the optional servers SO₁ . . . SO_(p) (22), which reside on thenetwork 24.

The client-server multitasking process 99 starts at step 101. The userU_(n) (12) enters the user input UI_(n) (25) into the user interfaceI_(n) (14) (step 102). The user input UI_(n) (25) is formulated into theuser service and/or information request iq_(n) (27) at the userinterface I_(n) (14) and communicated to the client C_(n) (16) (step103). The user service and/or information request iq_(n) (27) may beformulated into the service and/or information request IQ_(n) (28) atthe client C_(n) (16) and communicated to the server PS (18) (also step103).

The service and/or information response IR_(n) (34) and/or the userservice and/or information response ir_(n) (36) are derived at theserver PS (18) and/or the client C_(n) (16), respectively, at step 104,which in itself is a process, and may hereinafter be referred to as themultitasking process 104. The multitasking process 104 will be discussedin more detail later with reference to FIGS. 71 and 72.

Now, continuing with FIG. 70, the user service and/or informationresponse ir_(n) (36) may be derived at the client C_(n) (16) (step 104)from the service and/or information response IR_(n) (34), which may becommunicated to the client C_(n) (16) from the server PS (18) (also step104), and/or alternatively and/or additionally from the responses R_(n1). . . R_(nm) (32), which may be communicated to the client C_(n) (16)(step 104).

Now, the client C_(n) (16) may communicate the service and/orinformation request IQ_(n) (28) to the server PS (18) (step 103). Theservice and/or information response IR_(n) (34) is then derived at theserver PS (18) (step 104) and communicated to the client C_(n) (16)(also step 104). The user service and/or information response ir_(n)(36) may be derived from the service and/or information response IR_(n)(34) (also step 104).

Now, in more detail, if the service and/or information request IQ_(n)(28) is communicated to the server PS (18) (step 103), then the serverPS (18) makes the requests Q_(n1) . . . Q_(nm) (29) and/or certain onesof the requests Q_(n1) . . . Q_(nm) (29) of the servers S₁ . . . S_(z)(20), in accordance with the designation scheme which designates thecertain ones of the servers S₁ . . . S_(z) (20) to be communicated withcorresponding to the requests Q_(n1) . . . Q_(nm) (29) as thecorresponding server designations S_(n1) . . . S_(nm) (30), utilizinginformation from the service and/or information request IQ_(n) (28). Theservice and/or information response IR_(n) (34) is then derived at theserver PS (18) (step 104) from the responses R_(n1) . . . R_(nm) (32)received from the servers S₁ . . . S_(z) (20) corresponding to theserver designations S_(n1) . . . S_(nm) (30), and communicated to theclient C_(n) (16). Now, again, the user service and/or informationresponse ir_(n) (36) may be derived from the service and/or informationresponse IR_(n) (34) (also step 104).

Now, also in more detail, alternatively and/or additionally, the clientC_(n) (16) may make the requests Q_(n1) . . . Q_(nm) (29) and/or certainother ones of the requests Q_(n1) . . . Q_(nm) (29) of the servers S₁ .. . S_(z) (20), in accordance with the designation scheme whichdesignates the certain ones of the servers S₁ . . . S_(z) (20) to becommunicated with corresponding to the requests Q_(n1) . . . Q_(nm) (29)as the corresponding server designations S_(n1) . . . S_(nm) (30),utilizing information from the user service and/or information requestiq_(n) (27). Now, again, the user service and/or information responseir_(n) (36) may also be derived at the client C_(n) (16) (step 104) fromthe responses R_(n1) . . . R_(nm) (32) communicated to the client C_(n)(16) (step 104) and/or alternatively and/or additionally from theservice and/or information response IR_(n) (34) communicated to theclient C_(n) (16) from the server PS (18) (also step 104).

The user service and/or information response ir_(n) (36), thus, may bederived from the service and/or information response IR_(n) (34)communicated from the server PS (18) to the client C_(n) (16) and/oralternatively and/or additionally from the responses R_(n1) . . . R_(nm)(32) communicated to the client C_(n) (16) (step 104).

The user service and/or information response ir_(n) (36) is communicatedto the user interface I_(n) (14) (step 105) and incorporated into theuser response UR_(n) (37).

The user U_(n) (12) reviews the user response UR_(n) (37) and/or selectsadditional services and/or information (step 106). Step 106 will bediscussed in more detail later with reference to FIG. 76. The process 99ends at step 107. The process 99 will be described in more detail withreference to FIGS. 1-147 of the drawings.

The service and/or information response IR_(n) (34) and/or the userservice and/or information response ir_(n) (36) are derived at theserver PS (18) and/or the client C_(n) (16), respectively, at step 104in FIG. 70, and shown in more detail in FIGS. 71 and 72.

FIG. 71 shows the multitasking process 104 of deriving the serviceand/or information response IR_(n) (34) and/or the user service and/orinformation response ir_(n) (36), with reference to FIGS. 59 and 63.FIG. 72 shows the multitasking process 104 of deriving the serviceand/or information response IR_(n) (34) and/or the user service and/orinformation response ir_(n) (36) having other grouping/sorting that maybe used additionally and/or alternatively to that of FIGS. 59 and 63, asshown with reference to FIGS. 60 and 64. The multitasking process 104will also be described in more detail with reference to FIGS. 1-147 ofthe drawings.

The server PS (18) and/or the client C_(n) (16) parse, process, and/orformat the service and/or information request IQ_(n) (28) and/or theuser service and/or information request iq_(n) (27) into the currentrequest group QA_(nc) (50), the request groups QA_(n1) . . . QA_(nz)(51), and the optional instructions VJ_(n1) . . . VJ_(nk) (52) (step104-1), as shown in FIGS. 71 and 72.

Information from the current request group QA_(nc) (50) and the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) may be used to make the requestsQ_(n1) . . . Q_(nm) (29), obtain the responses R_(n1) . . . R_(nm) (32),and incorporate information therefrom into the service and/orinformation response IR_(n) (34) and/or the user service and/orinformation response ir_(n) (36), as shown in FIGS. 71 and 72 withreference to FIGS. 59, 60, 63, and 64. The current request group QA_(nc)(50) may be any particular one the request groups QA_(n1) . . . QA_(nz)(51), which may be selected by the user U_(n) (12).

The current request group QA_(nc) (50) has the corresponding queriesQQ_(n1) . . . QQ_(nm) (53) and the corresponding server addressesAQ_(n1) . . . AQ_(nm) (54) to open connections with and make therequests Q_(n1) . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20), inaccordance with the designation scheme which designates the certain onesof the servers S₁ . . . S_(z) (20) to be communicated with correspondingto the requests Q_(n1) . . . Q_(nm) (29) as the corresponding serverdesignations S_(n1) . . . S_(nm) (30), shown for the particular serviceand/or information request IQ_(n) (28) and/or the particular userservice and/or information request iq_(n) (27).

The server PS (18) and/or the client C_(n) (16) open connections withand make the requests Q_(n1) . . . Q_(nm) (29) having the correspondingqueries QQ_(n1) . . . QQ_(nm) (53) and the corresponding serveraddresses AQ_(n1) . . . AQ_(nm) (54) in the current request groupQA_(nc) (50) of the servers S₁ . . . S_(z) (20) (step 104-2) as shown inFIGS. 71 and 72, in accordance with the designation scheme whichdesignates the certain ones of the servers S₁ . . . S_(z) (20) to becommunicated with corresponding to the requests Q_(n1) . . . Q_(nm) (29)as the corresponding server designations S_(n1) . . . S_(nm) (30).

The servers S₁ . . . S_(z) (20) corresponding to the server designationsS_(n1) . . . S_(nm) (30), designated in accordance with the designationscheme which designates the certain ones of the servers S₁ . . . S_(z)(20) to be communicated with corresponding to the requests Q_(n1) . . .Q_(nm) (29) as the corresponding server designations S₁₁ . . . S_(nm)(30), respond to the requests Q_(n1) . . . Q_(nm) (29) with thecorresponding responses R_(n1) . . . R_(nm) (32).

The server PS (18) and/or the client C_(n) (16) parse, and/or process,and/or format, and/or group, and/or organize each of the responsesR_(n1) . . . R_(nm) (32) received from the servers S₁ . . . S_(z) (20)(step 104-3), as shown in FIGS. 71 and 72 with reference to FIGS.105-107, corresponding to the server designations S_(n1) . . . S_(nm)(30) into the corresponding addressable response information groupsRG_(n1) . . . RG_(nm) (57).

The server PS (18) and/or the client C_(n) (16) may also make additionaloptional requests QP_(n1) . . . QP_(nm) (58) of the optional databases41 and/or 42 (also step 104-2 of FIGS. 71 and 72), which may beoptionally resident within the server PS (18) and/or the client C_(n)(16), and which may reply with the corresponding additional optionalresponses RA_(n1) . . . RA_(nm) (40). The server PS (18) and/or theclient C_(n) (16) parse, and/or process, and/or format, and/or group,and/or organize each of the additional optional responses RA_(n1) . . .RA_(nm) (40) into the corresponding response information groups RC_(n1). . . RC_(nm) (59) (also step 104-3 of FIGS. 71 and 72).

Now, step 104-3 of FIGS. 71 and 72 is shown in more detail in FIG. 73.

As discussed later, and shown in FIGS. 105-107, entity body RH_(nm)(353) of the response R_(nm) (32) has optional response individualinformation groups LS_(nm1) . . . LS_(nmr) (360).

Each of the optional response individual information groups LS_(n11) . .. LS_(nmr) (360) and/or portions thereof from the entity bodies RH_(n1). . . RH_(nm) (353) of the responses R_(n1) . . . R_(nm) (32) may beoptionally compared one with the other, and duplicate ones of theoptional response individual information groups LS_(n11) . . . LS_(nmr)(360) may be optionally discarded (step 104-3-1), as shown in FIG. 73.

The remaining optional response individual information groups LS_(n11) .. . LS_(nmr) (360) are parsed, and/or processed, and/or formatted,and/or organized, and/or grouped into corresponding ones of theaddressable individual information groups LG_(n11) . . . LG_(nmr) (80)as the addressable individual information groups LG_(n11) . . . LG_(nmr)(80) are incorporated into the addressable response information groupsRG_(n1) . . . RG_(nm) (57) from the responses R_(n1) . . . R_(nm) (32)(step 104-3-2), as shown in FIG. 73.

The addressable individual information groups LG_(n11) . . . LG_(nmr)(80) are typically parsed, and/or processed, and/or formatted forconsistency of presentation and/or appearance one with the other, as theaddressable individual information groups LG_(n11) . . . LG_(nmr) (80)are incorporated into the addressable response information groupsRG_(n1) . . . RG_(nm) (57) from the responses R_(n1) . . . R_(nm) (32).

The server PS (18) and/or the client C_(n) (16) may formulateinformation from the current request group QA_(nc) (50) having thecorresponding queries QQ_(n1) . . . QQ_(nm) (53) and the correspondingserver addresses AQ_(n1) . . . AQ_(nm) (54) into the correspondingrequest pointer/address group QZ_(n) (60) having the pointers/addressesPG_(n1) . . . PG_(nz) (61) associated therewith (step 104-4 of FIG. 71with reference to FIGS. 59, 63, and 97). Alternatively and/oradditionally, the server PS (18) and/or the client C_(n) (16) mayformulate information from the current request group QA_(nc) (50) havingthe corresponding queries QQ_(n1) . . . QQ_(nm) (53) and thecorresponding server addresses AQ_(n1) . . . AQ_(nm) (54) into acorresponding request pointer/address group QY_(n) (68) having thepointers/addresses PF_(n11) . . . PF_(nmr) (69) associated therewith(step 104-4 of FIG. 72 with reference to FIGS. 60 and 64).

The server PS (18) and/or the client C_(n) (16) may formulate theaddressable query pointer/address groups QG_(n1) . . . QG_(nz) (62)(step 104-5 of FIG. 71 with reference to FIGS. 59, 63, 97, and 102, andtypical ones of the addressable query pointer/address groups QG_(n1) . .. QG_(nz) (62) in FIGS. 98 and 99), depending upon the grouping and/orsorting criteria used. Each of the pointers/addresses PG_(n1) . . .PG_(nz) (61) may be directed to point/address the correspondingaddressable query pointer/address groups QG_(n1) . . . QG_(nz) (62)associated therewith, which aid in obtaining information and/or servicesfrom certain ones of addressable response information groups RG_(n1) . .. RG_(nm) (57) to be incorporated into addressable query informationgroups GI_(n1) . . . GI_(nz) (63).

Each of the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) has the pointers/addresses PP_(n11) . . . PP_(nmr) (64)directed to address/point information in the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) based upon the groupingand/or sorting criteria.

The grouping and/or sorting criteria may be incorporated into theoptional instructions VJ_(n1) . . . VJ_(nk) (52), which may be enteredinto the user interface I_(n) (14) through the user input UI_(n) (25) bythe user U_(n) (12). Grouping and/or sorting criteria may additionallyand/or alternatively optionally resident within the server PS (18)and/or the client C_(n) (16).

The grouping and/or sorting criteria gives the user U_(n) (12) theability to formulate the query information groups GI_(n1) . . . GI_(nz)(63) and the way in which information and/or services from theaddressable response information groups RG_(n1) . . . RG_(nm) (57) ispresented to the user U_(n) (12) through the user interface I_(n) (14).

Information and/or services within each of the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57) is addressed with thepointers/addresses PP_(n11) . . . PP_(nmr) (64) from the querypointer/address groups QG_(n1) . . . QG_(nz) (62), and informationand/or services from the addressable response information groups RG_(n1). . . RG_(nm) (57) is incorporated into the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) corresponding to thepointers/addresses PP_(n11) . . . PP_(nmr) (64) (step 104-6 of FIG. 71),which are formulated by the addressable query pointer/address groupsQG_(n1) . . . QG_(nz) (62), in accordance with the grouping and/orsorting criteria, as shown in FIG. 71 with reference to FIGS. 59, 63,66A, 66B, 66C, 67-69, 97, and 102, typical ones of the addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62) in FIGS. 98 and 99,and a typical one of the addressable query information groups GI_(n1) .. . GI_(nz) (63), designated as the addressable query information groupGI_(nz) (63), in FIG. 109.

Alternatively and/or additionally, each of the pointers/addressesPF_(n11) . . . PF_(nmr) (69) may directed to point/address thecorresponding addressable response information groups RG_(n1) . . .RG_(nm) (57), and aid in obtaining information and/or services from thecorresponding addressable response information groups RG_(n1) . . .RG_(nm) (57) to be incorporated into the addressable query informationgroups GI_(n1) . . . GI_(nz) (63) (step 104-6) as shown FIG. 72 withreference to FIGS. 60, 64, 66A, 66B, 66C, and 67-69, and another typicalone of the addressable query information groups GI_(n1) . . . GI_(nz)(63), designated as the addressable query information group GI_(nz)(63), in FIG. 110.

Now, step 104-6 of FIG. 71 is shown in more detail in FIG. 74 withreference to FIGS. 59, 63, 66A, 66B, 66C, 67-69, 97, and 102, typicalones of the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) in FIGS. 98 and 99, and a typical one of the addressablequery information groups GI_(n1) . . . GI_(nz) (63), designated as theaddressable query information group GI_(nz) (63), in FIG. 109. Step104-6 of FIG. 72 is shown in more detail in FIG. 75 with reference toFIGS. 60, 64, 66A, 66B, 66C, and 67-69, and another typical one of theaddressable query information groups GI_(n1) . . . GI_(nz) (63),designated as the addressable query information group GI_(nz) (63), inFIG. 110.

The optional addressable individual information groups LG_(n11) . . .LG_(nmr) (80) in each of the addressable response information groupsRG_(n1) . . . RG_(nm) (57) may be addressed with the pointers/addressesPP_(n11) . . . PP_(nmr) (64) (step 104-6-1) as shown FIG. 74 withreference to FIGS. 59 and 63 and FIG. 71.

The optional addressable individual information groups LG_(n11) . . .LG_(nmr) (80) in each of the addressable response information groupsRG_(n1) . . . RG_(nm) (57) may alternatively and/or additionally beaddressed with the pointers/addresses PF_(n11) . . . PF_(nmr) (69) (step104-6-1) as shown FIG. 75 with reference to FIGS. 60 and 64 and FIG. 72.

The addressed optional addressable individual information groupsLG_(n11) . . . LG_(nmr) (80) and/or portions thereof may be optionallylabelled with labels and/or identifiers and incorporated into thelabelled individual information groups LL_(nz1) . . . LL_(nzu) (86)(step 104-6-2), as shown in FIGS. 74 and 75.

The labelled individual information groups LL_(n11) . . . LL_(nzu) (86)may be incorporated into certain ones of the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63), depending upon thegrouping and/or sorting criteria (step 104-6-3), as shown in FIGS. 74and 75.

The addressed optional addressable individual information groupsLG_(n11) . . . LG_(nmr) (80) and/or portions thereof are typicallyappended with the labels and/or identifiers, thus creating the labelledindividual information groups LL_(nz1) . . . LL_(nzu) (86), as each ofthe labelled individual information groups LL_(nz1) . . . LL_(nzu) (86)are incorporated into the certain ones of the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63). The steps 104-6-2 and104-6-3 are thus typically consolidated into a single step.

The addressable query information groups GI_(n1) . . . GI_(nz) (63) maythen be incorporated into the service and/or information response IR_(n)(34) (step 104-7), as shown in FIGS. 71 and 72 with reference to FIG.61, and/or the user service and/or information response ir_(n) (36)(also step 104-7), as also shown in FIGS. 71 and 72 but with referenceto FIG. 65.

The user U_(n) (12) reviews the user response UR_(n) (37) the userinterface I_(n) (14) and/or selects additional services and/orinformation at step 106 in FIG. 70, and shown in more detail in FIG. 76.The step 106 will also be described in more detail with reference toFIGS. 1-147 of the drawings.

The user U_(n) (12) selects additional services and/or informationthrough the user interface I_(n) (14) (step 106-1) or exits to the endof the process 99 at step 107. If the user U_(n) (12) selects additionalservices and/or information through the user interface I_(n) (14) (step106-1), the user U_(n) (12) may optionally enter one or more orders intoan order form and/or order forms at and through the user interface I_(n)(14) (step 106-2). The order and/or orders may be, for example, forpurchases, and/or instructions, and/or payment, and/or other informationand/or services to be directed to and/or requested of third parties,and/or combinations thereof, of the optional servers SO₁ . . . SO_(p)(22), and/or the servers S₁ . . . S_(z) (20), and/or other ones of theclients C₁ . . . C_(n) (16) through the server PS (18) and/or the clientC_(n) (16). The order and/or orders may, thus, be placed through and bythe server PS (18) and/or the client C_(n) (16), eliminating the needfor the user U_(n) (12) to place separate ones of the orders with thethird parties, the optional servers SO₁ . . . SO_(p) (22), and/or theservers S₁ . . . S_(z) (20) separately and/or individually.

The server PS (18) and/or the client C_(n) (16) process the ordersand/or communicate the orders to the third parties, the optional serversSO₁ . . . SO_(p) (22), and/or the servers S₁ . . . S_(z) (20), and/orother ones of the clients C₁ . . . C_(n) (16) (step 106-3). The serverPS (18) and/or the client C_(n) (16) confirm the order (step 106-4). Theuser U_(n) (12) may select additional services and/or informationthrough the user interface I_(n) (14) (step 106-1) or exit to the end ofthe process 99 at step 107.

If the user U_(n) (12) selects additional services and/or informationthrough the user interface I_(n) (14) (step 106-1), the user U_(n) (12)may alternatively and/or additionally optionally enter informationand/or service requests of the optional servers SO₁ . . . SO_(p) (22),and/or the servers S₁ . . . S_(z) (20) through the user interface I_(n)(14) (step 106-5) and/or exit to the end of the process 99 at step 107.

If the user U_(n) (12) selects additional services and/or informationthrough the user interface I_(n) (14) (step 106-1), the user U_(n) (12)may alternatively and/or additionally optionally enter additionalrequests as the user input UI_(n) (25) at and through the user interfaceI_(n) (14) (step 106-6) and enter the process 99 at step 102.

V. Additional Details

A. User Input

The user input UI_(n) (25), which the user U_(n) (12) makes through theuser interface I_(n) (14), may have one or a plurality of the sameand/or different ones of the queries QQ_(n1) . . . QQ_(nm) (53) to bemade by the server PS (18) and/or the client C_(n) (16) of the sameand/or different ones of the servers S₁ . . . S_(z) (20), in accordancewith the designation scheme which designates the servers S₁ . . . S_(z)(20) to be communicated with corresponding to the requests Q_(n1) . . .Q_(nm) (29) as the corresponding server designations S_(n1) . . . S_(nm)(30) at the corresponding server addresses AQ_(n1) . . . AQ_(nm) (54).

The server PS (18) and/or the client C_(n) (16) parse, process, format,sort, group, and/or organize each of the responses R_(n1) . . . R_(nm)(32) to the corresponding requests Q_(n1) . . . Q_(nm) (29), receivedfrom the servers S₁ . . . S_(z) (20) designated by the serverdesignations S_(n1) . . . S_(nm) (30), and/or each of the additionaloptional responses RA_(n1) . . . RA_(nm) (40) from the server PS (18)and/or the client C_(n) (16). The parsed, processed, formatted, sorted,grouped, and/or organized results from the server PS (18) and/or theclient C_(n) (16) are communicated to the user U_(n) (12) through theuser interface I_(n) (14) as the user response UR_(n) (37), which theuser U_(n) (12) may review, interact with, and/or select additionalservices and/or information therefrom.

The user U_(n) (12) enters the user input UI_(n) (25) having one or moreof the same and/or different user requests qu_(n1) . . . qu_(nu) (26)into the user interface I_(n) (14), as shown in FIG. 3. The userrequests qu_(n1) . . . qu_(nu) (26) are communicated from the userinterface I_(n) (14) to the client C_(n) (16) within the user serviceand/or information request iq_(n) (27), having the user requests qu_(n1). . . qu_(nu) (26) and other optional information.

The user U_(n) (12) may enter the user input UI_(n) (25) having one ormore of the same and/or different user requests qu_(n1) . . . qu_(nu)(26) into the service and/or information entry request form IE_(n) (38)at the user interface I_(n) (14), or into the user interface I_(n) (14)through other suitable means.

The user interfaces I₁ . . . I_(n) (14) have suitable input means and/orsuitable presentation and/or display means, which allow thecorresponding users U₁ . . . U_(n) (12) to communicate with thecorresponding clients C₁ . . . C_(n) (16). FIGS. 5A, 5B, and 6-10 showtypical ones of the service and/or information entry request forms IE₁ .. . IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14), as graphicaluser interfaces (GUI's), which the users U₁ . . . U_(n) (12) may enterthe corresponding user inputs UI₁ . . . UI_(n) (25) thereinto. FIGS. 77and 78 are schematic representations of the service and/or informationentry request form IE_(n) (38) showing fields, links, and elements ofthe service and/or information entry request form IE_(n) (38).

The user U_(n) (12) may enter the user input UI_(n) (25) into theservice and/or information entry request form IE_(n) (38) at the userinterface I_(n) (14), as shown schematically in FIG. 77. The user inputUI_(n) (25) may be entered as user input values into fields or alternaterequest links of the service and/or information entry request formIE_(n) (38).

The user U_(n) (12) may enter the user input UI_(n) (25) as one or moreof the same and/or different user requests qu_(n1) . . . qu_(nu) (26),which may have the query values QV_(n1) . . . QV_(nu) (200), server namevalues AV_(n1) . . . AV_(nu) (201), optional instruction values VV_(n1). . . VV_(nv () 202), and/or alternate request links QL_(n1) . . .QL_(na) (203), and/or server request links UL_(n1) . . . UL_(ns) (204),and/or the additional request links SL_(n1) . . . SL_(nw) (71) into theservice and/or information entry request form IE_(n) (38).

The user input UI_(n) (25), thus, has one or more of the same and/ordifferent user requests qu_(n1) . . . qu_(nu) (26), which may be enteredas the query values QV_(n1) . . . QV_(nu) (200) of the same and/ordifferent servers S₁ . . . S_(z) (20), designated in accordance with thedesignation scheme corresponding to the corresponding certain ones ofthe server designations S₁₁ . . . S_(nm) (30) having the correspondingserver name values AV_(n1) . . . AV_(nu) (201), the optional instructionvalues VV_(n1) . . . VV_(nv) (202), and/or the alternate request linksQL_(n1) . . . QL_(na) (203), and/or the server request links UL_(n1) . .. UL_(ns) (204), and/or the additional request links SL_(n1) . . .SL_(nw) (71) into the service and/or information entry request formIE_(n) (38).

Each of the different user requests qu_(n1) . . . qu_(nu) (26) may bethe same and/or different one from the other. Each of the query valuesQV_(n1) . . . QV_(nu) (200) may be the same and/or different one fromthe other. The query values QV_(n1) . . . QV_(nu) (200) may be enteredfor the same and/or different ones of the servers S₁ . . . S_(z) (20).The optional instruction values VV_(n1) . . . VV_(nv) (202) may be thesame and/or different one from the other.

The user U_(n) (12) may also enter the user input UI_(n) (25) andrequest services and/or information through one of the alternate requestlinks QL_(n1) . . . QL_(na) (203), or one of the server request linksUL_(n1) . . . UL_(ns) (204), or one of the additional request linksSL_(n1) . . . SLnw (71) at the user interface I_(n) (14).

B. User Interface Details

The client-server multitasking system 10 of the present invention mayhave any suitable user interface I_(n) (14) acceptable to and/orpreferred by the user U_(n) (12), and acceptable to the client C_(n)(16). The user interface I_(n) (14) may be, for example, a graphicaluser interface, visual, aural, and/or tactile user interface, and/orcombination thereof, or other suitable interface. The user interfaceI_(n) (14) may be integral with the client C_(n) (16) or separatetherefrom.

The user interface I_(n) (14) may be hardware based, and/or computerbased, and/or process based, and/or a combination thereof, and may be agraphical user interface, such as, for example, a browser and/orcombinations thereof, varieties of which are commonly used on theinternet.

The service and/or information entry request form IE_(n) (38) may beoptionally available to the user U_(n) (12) at the user interface I_(n)(14), or the user U_(n) (12) may optionally request the service and/orinformation entry request form IE_(n) (38) through the user interfaceI_(n) (14).

Now, as shown in FIGS. 5A, 5B, and 6-10 and schematically in FIGS. 77and 78, the service and/or information entry request form IE_(n) (38) atthe user interface I_(n) (14) has user client request fields QD_(n1) . .. QD_(nu) (206) accessible to the user U_(n) (12) and hidden clientrequest elements HU_(n1) . . . HU_(nh) (207) hidden from the user U_(n)(12). The user client request fields QD_(n1) . . . QD_(nu) (206)accessible to the user U_(n) (12) has server requests portion 208,optional instructions portion 209, an optional execute request element210, and alternate requests portion 212. The hidden client requestelements HU_(n1) . . . HU_(nh) (207) hidden from the user U_(n) (12)have optional server requests portion 214, optional instructions portion216, and optional information element HE_(n) (218).

The server requests portion 208 of the user client request fieldsQD_(n1) . . . QD_(nu) (206) accessible to the user U_(n) (12) has serverquery fields QF_(n1) . . . QF_(nu) (220), which the user U_(n) (12) mayenter corresponding server query values QV_(n1) . . . QV_(nu) (200)thereinto, as a portion of the user input UI_(n) (25).

The user U_(n) (12) may also optionally enter the server name valuesAV_(n1) . . . AV_(nu) (201) into server name fields AF_(n1) . . .AF_(nu) (224). The user U_(n) (12) may enter the server name valuesAV_(n1) . . . AV_(nu) (201) as another portion of the user input UI_(n)(25).

The user U_(n) (12) may also optionally enter the optional instructionvalues VV_(n1) . . . VV_(nv) (202) into optional instruction fieldsVF_(n1) . . . VF_(nv) (228) of the optional instructions portion 209 ofthe user client request fields QD_(n1) . . . QD_(nu) (206) accessible tothe user U_(n) (12). The user U_(n) (12) may enter the optionalinstruction values VV_(n1) . . . VV_(nv) (202) as yet another portion ofthe user input UI_(n) (25).

Upon the user U_(n) (12) entering the user input UI_(n) (25) of theserver query values QV_(n1) . . . QV_(nu) (200) and/or the server namevalues AV_(n1) . . . AV_(nu) (201) and/or the optional instructionvalues VV_(n1) . . . VV_(nv) (202) into the service and/or informationentry request form IE_(n) (38) at the user interface I_(n) (14), thecompleted service and/or information request form IF_(n) (230) results,shown schematically in FIGS. 79 and 80.

The user U_(n) (12) may instruct the user interface I_(n) (14) tocommunicate the user service and/or information requests iq_(n) (27),shown in FIG. 80, having the server query values QV_(n1) . . . QV_(nu)(200) and/or the server name values AV_(n1) . . . AV_(nu) (201) and/orthe optional instruction values VV_(n1) . . . VV_(nv) (202), from thealready completed service and/or information request form IF_(n) (230)at the user interface I_(n) (14) to the client C_(n) (16) by enteringthe optional execute request element 210, using a point and clickdevice, such as a mouse, light pen, tactile monitor, by entering acarriage return, through other user interface controls, or through othersuitable means. FIG. 81 shows a schematic representation of the userservice and/or information request iq_(n) (27).

The user U_(n) (12) may alternatively enter the alternate request linksQL_(n1) . . . QL_(na) (203) or the server request links UL_(n1) . . .UL_(ns) (204) or the additional request links SL_(n1) . . . SL_(nw) (71)into the service and/or information entry request form IE_(n) (38) witha point and click device, such as a mouse, a light pen, tactile monitor,or with alternative and/or other user interface controls or othersuitable means, and instruct the user interface I_(n) (14) tocommunicate the user service and/or information request iq_(n) (27),having information associated with the alternate request links QL_(n1) .. . QL_(na) (203) or the server request links UL_(n1) . . . UL_(ns)(204) or the additional request links SL_(n1) . . . SL_(nw) (71), to theclient C_(n) (16).

The server name fields AF_(n1) . . . AF_(nu) (224) and the optionalinstruction fields VF_(n1) . . . VF_(nv) (228) of the service and/orinformation entry request form IE_(n) (38) may optionally have theserver name values AV_(n1) . . . AV_(nu) (201) and/or the optionalinstruction values VV_(n1) . . . VV_(nv) (202) entered thereinto,respectively, as changeable and/or fixed pre-set or preselected values,drop down menu selections, and/or as blank fields, or a combinationthereof. The preselected values may be replaced with values of theuser's U_(n) (12) choice or may remain fixed, depending upon choicesoffered in the service and/or information entry request form IE_(n)(38). The drop down menu selections may be changed to ones of a numberof preselected choices offered in the drop down menu selections, whichthe user U_(n) (12) may optionally scroll through to determine whichchoice to make. Blank ones of the server name fields AF_(n1) . . .AF_(nu) (224) and/or blank ones of the optional instruction fieldsVF_(n1) . . . VF_(nv) (228) allow the user U_(n) (12) to optionallyenter the server name values AV_(n1) . . . AV_(nu) (201) and/or theoptional instruction values VV_(n1) . . . VV_(nv) (202), respectively,therein, accordingly.

The server query fields QF_(n1) . . . QF_(nu) (220), which the userU_(n) (12) enters the corresponding server query values QV_(n1) . . .QV_(nu) (200) thereinto, through the user input UI_(n) (25), may alsohave changeable and/or fixed preselected values, drop down menuselections, and/or blank fields, or a combination thereof. However, theserver query fields QF_(n1) . . . QF_(nu) (220) may generally bepresented to the user U_(n) (12) as blank fields, at least for the firstuser input UI_(n) (25).

The alternate requests portion 212 of the user client request fieldsQD_(n1) . . . QD_(nu) (206) accessible to the user U_(n) (12) has thealternate request links QL_(n1) . . . QL_(na) (203), the server requestlinks UL_(n1) . . . UL_(ns) (204), and the additional request linksSL_(n1) . . . SL_(nw) (71). The user U_(n) (12) may alternativelyrequest services and/or information through one of the alternate requestlinks QL_(n1) . . . QL_(na) (203), or one of the server request linksUL_(n1) . . . UL_(ns) (204), or one of the additional request linksSL_(n1) . . . SL_(nw) (71).

The alternate request links QL_(n1) . . . QL_(na) (203) allow the userU_(n) (12) to make the service and/or information request IQ₁ . . .IQ_(n) (28) with preconfigured optional default selections alreadyplaced in the service and/or information request IQ₁ . . . IQ_(n) (28)for the user U_(n) (12). The server request links UL_(n1) . . . UL_(nw)(204) may be advertisements, advertising links, and/or links to ones ofthe optional servers SO₁ . . . SO_(p) (22). The user U_(n) (12) may, forexample, make requests for additional services and/or information fromones of the optional servers SO₁ . . . SO_(p) (22), using the serverrequest links UL_(n1) . . . UL_(nw) (204). The additional request linksSL_(n1) . . . SL_(nw) (71) allow the user U_(n) (12) to make additionaloptional selections, based upon information and/or services previouslyrequested by the user U_(n) (12).

The optional server requests portion 214 of the hidden client requestelements HU_(n1) . . . HU_(nh) (207) hidden from the user U_(n) (12) hashidden query elements Qh_(n1) . . . Qh_(nh) (236) and correspondingassociated hidden server name elements Ah_(n1) . . . Ah_(nh) (238). Theoptional instructions portion 216 of the hidden client request elementsHU_(n1) . . . HU_(nh) (207) hidden from the user U_(n) (12) may haveoptional hidden instruction elements Vh_(n1) . . . Vh_(ni) (240). Thehidden client request elements HU_(n1) . . . HU_(nh) (207) hidden fromthe user U_(n) (12) may also have the hidden optional informationelement HE_(n) (218), which may have optional information and/orstatistics.

The user U_(n) (12) may, thus, request the services and/or informationby completing entry of the server requests portion 208 and the optionalinstructions portion 209 with the optional execute request element 210,after entering the server query values QV_(n1) . . . QV_(nu) (200)and/or the server name values AV_(n1) . . . AV_(nu) (201) and/or theoptional instruction values VV_(n1) . . . VV_(nv) (202), or byalternatively requesting the services and/or information through one ofthe alternate request links QL_(n1) . . . QL_(na) (203), or one of theserver request links UL_(n1) . . . UL_(ns) (204), or one of theadditional request links SL_(n1) . . . SL_(nw) (71).

Upon completion of the user input UI_(n) (25), the completed serviceand/or information request form IF_(n) (230), as shown in FIGS. 79 and80, has user client request elements QM_(n1) . . . QM_(nu) (246)accessible to the user U_(n) (12) having server request elements 242 andoptional instruction elements VE_(n1) . . . VE_(nv) (244); and/oralternate request elements 248 of the user client request elementsQM_(n1) . . . QM_(nu) (246) accessible to the user U_(n) (12); and/oroptional server request elements 250, optional instruction elements 252,and/or hidden client request elements HP_(n1) . . . HP_(nh) (256) hiddenfrom the user U_(n) (12).

The user U_(n) (12) may instruct the user interface I_(n) (14) tocommunicate the user service and/or information request iq_(n) (27)derived from the service and/or information request form IF_(n) (230) tothe client C_(n) (16), as shown in FIG. 81, with the optional executerequest element 210 or with the other suitable means; or the user U_(n)(12) may alternatively communicate the user service and/or informationrequest iq_(n) (27) by entering the alternate request links QL_(n1) . .. QL_(na) (203) or the server request links UL_(n1) . . . UL_(ns) (204)or the additional request links SL_(n1) . . . SL_(nw) (71) into theservice and/or information entry request form IE_(n) (38) or into thecompleted service and/or information request form IF_(n) (230) with apoint and click device, such as a mouse, a light pen, tactile monitor,or with alternative and/or other user interface controls or othersuitable means, and instruct the user interface I_(n) (14) tocommunicate the user service and/or information request iq_(n) (27),having information associated with the alternate request links QL_(n1) .. . QL_(na) (203) or the server request links UL_(n1) . . . UL_(ns)(204) or the additional request links SL_(n1) . . . SL_(nw) (71), to theclient C_(n) (16).

FIGS. 79 and 80 are schematic representations of the completed serviceand/or information entry request form IF_(n) (230) showing typicalelements, values, field names, name-value pairs, optional instructions,and alternate requests, resulting from the user U_(n) (12) entering theuser input UI_(n) (25) of the server query values QV_(n1) . . . QV_(nu)(200) and/or the server name values AV_(n1) . . . AV_(nu) (201) and/orthe optional instruction values VV_(n1) . . . WV_(nv) (202) into theservice and/or information entry request form IE_(n) (38) at the userinterface I_(n) (14).

Now, the completed service and/or information entry request form IF_(n)(230) has the user client request elements QM_(n1) . . . QM_(nu) (246)accessible to the user U_(n) (12) having the server request elements242, which has query elements QE_(n1) . . . QE_(nu) (258) andcorresponding associated server name elements AE_(n1) . . . AE_(nu)(260).

Each of the query elements QE_(n1) . . . QE_(nu) (258) have query fieldnames QN_(n1) . . . QN_(nu) (262) of the associated corresponding serverquery fields QF_(n1) . . . QF_(nu) (220) and the corresponding serverquery values QV_(n1) . . . QV_(nu) (200) associated therewith, which therequests Q₁₁ . . . Q_(nm) (29) may be derived therefrom.

Each of the server name elements AE_(n1) . . . AE_(nu) (260) have serverfield names AN_(n1) . . . AN_(nm) (264) of the associated correspondingserver name fields AF_(n1) . . . AF_(nu) (224) and the correspondingserver name values AV_(n1) . . . AV_(nu) (201) associated therewith,which server addresses A_(n1) . . . A_(nu) (265) may be derivedtherefrom.

The user client request elements QM_(n1) . . . QM_(nu) (246) accessibleto the user U_(n) (12) also have the optional instruction elementsVE_(n1) . . . VE_(nv) (244) having optional instruction field namesVN_(n1) . . . VN_(nv) (266) of the associated corresponding optionalinstruction fields VF_(n1) . . . VF_(nv) (228) and the correspondingoptional instruction values VV_(n1) . . . VV_(nv) (202) associatedtherewith.

The user client request elements QM_(n1) . . . QM_(nu) (246) accessibleto the user U_(n) (12) also have the alternate request elements 246having the alternate request links QL_(n1) . . . QL_(na) (203), or theserver request links UL_(n1) . . . UL_(ns) (204), or the additionalrequest links SL_(n1) . . . SL_(nw) (71).

The hidden client request elements HP_(n1) . . . HP_(nh) (256) hiddenfrom the user U_(n) (12) have the hidden query elements Qh_(n1) . . .Qh_(nh) (236), which may have hidden query field names Qn_(n1) . . .Qn_(nh) (268) and corresponding hidden query values Qv_(n1) . . .Qv_(nh) (270) associated therewith. The hidden server name elementsAh_(n1) . . . Ah_(nh) (238) may have hidden server field names An_(n1) .. . An_(nh) (272) and corresponding server hidden request name valuesAv_(n1) . . . Av_(nh) (274) associated therewith.

The hidden client request elements HP_(n1) . . . HP_(nh) (256) hiddenfrom the user U_(n) (12) may also have the optional hidden instructionelements Vh_(n1) . . . Vh_(ni) (240), which may have optional hiddeninstruction field names Vn_(n1) . . . Vn_(ni) (275) and correspondingoptional hidden instruction values Vv_(n1) . . . Vv_(ni) (276)associated therewith. The hidden client request elements HP_(n1) . . .HP_(nh) (256) hidden from the user U_(n) (12) may also have the hiddenoptional information element HE_(n) (218), which may have optionalhidden information element field name Jn_(n) (277) and optional hiddeninformation element value Jv_(n) (278) associated therewith.

Now again, the user interfaces I₁ . . . I_(n) (14) may each bedifferent, one from the other, or the same, and may changecharacteristics over time. Each of the user interfaces I₁ . . . I_(n)(14) may change characteristics as a function of time, information,and/or instructions, and/or other means, which may be derived by theusers U₁ . . . U_(n) (12) and/or the clients C₁ . . . C_(n) (16) and/orthe servers S₁ . . . S_(z) (20), and/or the server PS (18), and/or theoptional servers SO₁ . . . SO_(p) (22), and/or derived within the userinterfaces I₁ . . . I_(n) (14). The user interface I₁ . . . I_(n) (14)may change state.

The user interface I₁ . . . I_(n) (14) may also change as a function ofoptional timers and/or timed instructions associated with the userinterfaces I₁ . . . I_(n) (14), and/or associated with the clients C₁ .. . C_(n) (16) and/or associated with the servers S₁ . . . S_(z) (20),and/or associated with the server PS (18), and/or associated with theoptional servers SO₁ . . . SO_(p) (22), and/or instructions from theuser U₁ . . . U_(n) (12). Changes in the user interface I_(n) (14) mayappear continuous to the user U_(n) (12), spaced in time, staccato, orstatic depending upon the optional timers and/or the timed instructions.Other conditions may change the user interface I₁ . . . I_(n) (14), aswell.

The user interfaces I₁ . . . I_(n) (14) may be updated continuously,intermittently, manually, randomly, semi-automatically, automatically,repetitively, non-repetitively, singly, plurally, multiplexed, and/or acombination thereof or other suitable manner.

The user interfaces I₁ . . . I_(n) (14) may be visual, such as graphicaluser interfaces, aural, and/or tactile, a combination thereof, and/orother suitable means. The user interfaces I₁ . . . I_(n) (14) may beintegral with the clients C₁ . . . C_(n) (16) or separate therefrom.

The user interfaces I₁ . . . I_(n) (14) may change in response to theuser inputs UI₁ . . . UI_(n) (25), the service and/or information entryrequest forms IE₁ . . . IE_(n) (38) at the user interfaces I₁ . . .I_(n) (14), the completed service and/or information request formsIF_(n) (230), the user service and/or information requests iq₁ . . .iq_(n) (27), the optional execute request elements 210, accessing thealternate request links QL₁₁ . . . QL_(1a) (203), accessing the serverrequest links UL₁₁ . . . UL_(1s) (204), accessing the additional requestlinks SL₁₁ . . . SL₁₁ (71), the service and/or information responses IR₁. . . IR_(n) (34), the service and/or information response forms IS₁ . .. IS_(n) (39). Other conditions may change the user interface I₁ . . .I_(n) (14), as well.

Portions of the user responses UR₁ . . . UR_(n) (37) may be mapped intoand/or onto different portions of the user interfaces I₁ . . . I_(n)(14) to facilitate interaction with and the needs of each of the usersU₁ . . . U_(n) (12). Such mappings may be optionally customized by theusers U₁ . . . U_(n) (12).

C. Service and/or Information Request Details

Each of the users U₁ . . . U_(n) (12) communicate the corresponding userservice and/or information requests iq₁ . . . iq_(n) (27) through thecorresponding user interfaces I₁ . . . I_(n) (14) to the correspondingclients C₁ . . . C_(n) (16), which optionally format the correspondinguser service and/or information requests iq₁ . . . iq_(n) (27) into thecorresponding service and/or information requests IQ₁ . . . IQ_(n) (28),as required.

Now, again, the user U_(n) (12) may instruct the user interface I_(n)(14) to communicate the user service and/or information requests iq_(n)(27), having the server query values QV_(n1) . . . QV_(nu) (200) and/orthe server name values AV_(n1) . . . AV_(nu) (201) and/or the optionalinstruction values VV_(n1) . . . VV_(nv) (202), from the alreadycompleted service and/or information request form IF_(n) (230) at theuser interface I_(n) (14) to the client C_(n) (16) by entering theoptional execute request element 210, using a point and click device,such as a mouse, light pen, tactile monitor, by entering a carriagereturn, through other user interface controls, or through other suitablemeans. FIG. 81 shows a schematic representation of the user serviceand/or information request iq_(n) (27).

The user U_(n) (12) may alternatively enter the alternate request linksQL_(n1) . . . QL_(na) (203) or the server request links UL_(n1) . . .UL_(ns) (204) or the additional request links SL_(n1) . . . SL_(nw) (71)into the service and/or information entry request form IE_(n) (38) witha point and click device, such as a mouse, a light pen, tactile monitor,or with alternative and/or other user interface controls or othersuitable means, and instruct the user interface I_(n) (14) tocommunicate the user service and/or information request iq_(n) (27),having information associated with the alternate request links QL_(n1) .. . QL_(na) (203) or the server request links UL_(n1) . . . UL_(ns)(204) or the additional request links SL_(n1) . . . SL_(nw) (71), to theclient C_(n) (16).

The user service and/or information request iq_(n) (27) is communicatedfrom the user interface I_(n) (14) to the client C_(n) (16), which actsupon the user service and/or information request iq_(n) (27) to derivethe service and/or information request IQ_(n) (28) therefrom. FIGS.81-86 are schematic representations of the service and/or informationrequest IQ_(n) (28) and/or the user service and/or information requestiq_(n) (27).

The service and/or information request IQ_(n) (28) has informationand/or elements, which may be used by the server PS (18) to make therequests Q_(n1) . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20), inaccordance with the designation scheme which designates the ones of theservers S₁ . . . S_(z) (20) to be communicated with corresponding to therequests Q₁₁ . . . Q_(nm) (29) as the corresponding server designationsS₁₁ . . . S_(nm) (30). The client C_(n) (16) may additionally and/oralternatively make the requests Q_(n1) . . . Q_(nm) (29) of the serversS₁ . . . S_(z) (20), using information and/or elements within the userservice and/or information request iq_(n) (27).

The service and/or information request IQ_(n) (28) has user clientrequests QC_(n1) . . . QC_(nu) (280) accessible to the user U_(n) (12)and hidden client requests HC_(n1) . . . HC_(nh) (281) hidden from theuser U_(n) (12).

The user client requests QC_(n1) . . . QC_(nu) (280) accessible to theuser U_(n) (12) and/or the hidden client requests HC_(n1) . . . HC_(nh)(281) hidden from the user U_(n) (12) have address and/or locationinformation and/or instructions, and/or other information correspondingto information and/or services to be requested of the servers S₁ . . .S_(z) (20), and/or information and/or instructions to be utilized by theserver PS (18) and/or ones of the clients C₁ . . . C_(n) (16).

The user client requests QC_(n1) . . . QC_(nu) (280) accessible to theuser U_(n) (12) have server requests portion SQ_(n) (282), optionalinstructions portion V_(n) (283), and alternate request portion AL_(n)(284).

The hidden client requests HC_(n1) . . . HC_(nh) (281) hidden from theuser U_(n) (12) has optional hidden server requests portion HQ_(n)(285), optional hidden instructions portion HO_(n) (286), and optionalhidden information portion J_(n) (287).

The server requests portion SQ_(n). (282) of the service and/orinformation request IQ_(n) (28) has queries QS_(n1) . . . QS_(nu) (288),which may be derived from the query field names QN_(n1) . . . QN_(nu)(262) and the corresponding server query values QV_(n1) . . . QV_(nu)(200) of the query elements QE_(n1) . . . QE_(nu) (258).

The server requests portion SQ_(n) (282) of the service and/orinformation request IQ_(n) (28) may also have the server addressesA_(n1) . . . A_(nu) (265), which may be derived from the server fieldnames AN_(n1) . . . AN_(nm) (264) and the corresponding server namevalues AV_(n1) . . . AV_(nu) (201) of the server name elements AE_(n1) .. . AE_(nu) (260).

The optional instructions portion VO_(n) (283) of the user clientrequests QC_(n1) . . . QC_(nu) (280) accessible to the user U_(n) (12)of the service and/or information request IQ_(n) (28) may have optionalinstructions V_(n1) . . . V_(nv) (289), which may be derived from theoptional instruction field names VN_(n1) . . . VN_(nv) (266) and thecorresponding optional instruction values VV_(n1) . . . VV_(nv) (202).The optional instructions V_(n1) . . . V_(nv) (289) may optionally beused by the client C_(n) (16) and/or the server PS (18), and/orincorporated into the requests Q_(n1) . . . Q_(nm) (29) to be made ofthe servers S₁ . . . S_(z) (20) designated by the server designationsS_(n1) . . . S_(nm) (30), corresponding to the requests Q_(n1) . . .Q_(nm) (29) associated with the user U_(n) (12).

The alternate request portion AL_(n) (284) of the user client requestsQC_(n1) . . . QC_(nu) (280) accessible to the user U_(n) (12) of theservice and/or information request IQ_(n) (28) may be derived from oneof the alternate request links QL_(n1) . . . QL_(na) (203), or one ofthe server request links UL_(n1) . . . UL_(ns) (204), or one of theadditional request links SL_(n1) . . . SL_(nw) (71).

The optional hidden server requests portion HQ_(n1) . . . HQ_(nh) (281)of the hidden client requests HC_(n1) . . . HC_(nh) (281) hidden fromthe user U_(n) (12) may have hidden queries QH_(n1) . . . QH_(nh) (290)and corresponding hidden server addresses AH_(n1) . . . AH_(nh) (291).

The hidden queries QH_(n1) . . . QH_(nh) (290) of the optional hiddenserver requests portion HQ_(n1) . . . HQ_(nh) (281) of the serviceand/or information request IQ_(n) (28) may be derived from the hiddenquery field names Qn_(n1) . . . Qn_(nh) (268) and the correspondinghidden query values Qv_(n1) . . . Qv_(nh) (270).

The hidden server addresses AH_(n1) . . . AH_(nh) (291) of the optionalhidden server requests portion HQ_(n1) . . . HQ_(nh) (281) of theservice and/or information request IQ_(n) (28) may be derived from thehidden server field names An_(n1) . . . An_(nh) (272) and thecorresponding server hidden server name values Av_(n1) . . . Av_(nh)(274).

The hidden queries QH_(n1) . . . QH_(nh) (290) may optionally beappended to the queries QS_(n1) . . . QS_(nu) (288) to be made of theservers S₁ . . . S_(z) (20). The hidden server addresses AH_(n1) . . .AH_(nh) (291) may optionally be appended to the server addresses A_(n1). . . A_(nu) (265). The appended queries QS_(n1) . . . QS_(nu) (288) maythen be made of the servers S₁ . . . S_(z) (20) designated by the serverdesignations S_(n1) . . . S_(nm) (30), corresponding to the resultingappended requests Q_(n1) . . . Q_(nm) (29) associated with the userU_(n) (12), in accordance with the appended server addresses A_(n1) . .. A_(nu) (265).

The appended requests Q_(n1) . . . Q_(nm) (29) will hereinafter be usedsynonymously with the requests Q_(n1) . . . Q_(nm) (29), the appendedqueries QS_(n1) . . . QS_(nu) (288) will hereinafter be usedsynonymously with the queries QS_(n1) . . . QS_(nu) (288), and theappended server addresses A_(n1) . . . A_(nu) (265) will hereinafter beused synonymously with the server addresses A_(n1) . . . A_(nu) (265).

The optional hidden instructions portion HO_(n) (286) of the hiddenclient requests HC_(n1) . . . HC_(nh) (281) hidden from the user U_(n)(12) of the service and/or information request IQ_(n) (28) have optionalhidden instructions H_(n1) . . . H_(ni) (292), which may be derived fromthe hidden instruction field names Vn_(n1) . . . Vn_(ni) (275) and thecorresponding optional hidden instruction values Vv_(n1) . . . Vv_(ni)(276). The optional hidden instructions H_(n1) . . . H_(ni) (292) mayoptionally be appended to the optional instructions V_(n1) . . . V_(nv)(289) and/or may optionally be used by the client C_(n) (16) and/or theserver PS (18), and/or incorporated into the requests Q_(n1) . . .Q_(nm) (29) to be made of the servers S₁ . . . S_(z) (20) designated bythe server designations S_(n1) . . . S_(nm) (30), corresponding to therequests Q_(n1) . . . Q_(nm) (29) associated with the user U_(n) (12).The appended instructions V_(n1) . . . V_(nv) (289) will hereinafter beused synonymously with the instructions V_(n1) . . . V_(nv) (289).

The optional hidden information portion J_(n) (287) of the hidden clientrequests HC_(n1) . . . HC_(nh) (281) hidden from the user U_(n) (12) ofthe service and/or information request IQ_(n) (28) may be derived fromthe optional hidden information element field name Jn_(n) (277) and theoptional hidden information element value Jv_(n) (278), and mayoptionally be used by the client C_(n) (16) and/or the server PS (18),and/or incorporated into the requests Q_(n1) . . . Q_(nm) (29) to bemade of the servers S₁ . . . S_(z) (20) designated by the serverdesignations S_(n1) . . . S_(nm) (30), corresponding to the requestsQ_(n1) . . . Q_(nm) (29) associated with the user U_(n) (12).

Now, again, each of the users U₁ . . . U_(n) (12) communicate thecorresponding user service and/or information requests iq₁ . . . iq_(n)(27) through the corresponding user interfaces I₁ . . . I_(n) (14) tothe corresponding clients C₁ . . . C_(n) (16), which optionally formatthe corresponding user service and/or information requests iq₁ . . .iq_(n) (27) into the corresponding service and/or information requestsIQ₁ . . . IQ_(n) (28), as required.

The user service and/or information requests iq₁ . . . iq_(n) (27) maybe communicated from the completed service and/or information entryrequest forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . . .I_(n) (14) to the clients C₁ . . . C_(n) (16) or alternatively from theservice and/or information entry request forms IE₁ . . . IE_(n) (38) atthe corresponding user interfaces I₁ . . . I_(n) (14) through thealternate request links QL₁₁ . . . QL_(na) (203) or the server requestlinks UL₁₁ . . . UL_(ns) (204) or the additional request links SL₁₁ . .. SL_(nw) (71).

The user service and/or information requests iq₁ . . . iq_(n) (27) maybe communicated as the elements, values, field names, optionalinstructions, and/or alternate requests entered into the completedservice and/or information entry request form IF_(n) (230) from thecorresponding user interfaces I₁ . . . I_(n) (14) to the correspondingclients C₁ . . . C_(n) (16).

The users U₁ . . . U_(n) (12) may, thus, communicate the correspondinguser service and/or information requests iq₁ . . . iq_(n) (27) to theclients C₁ . . . C_(n) (16) through the user interfaces I₁ . . . I_(n)(14), upon entering the corresponding user inputs UI₁ . . . UI_(n) (25)into the corresponding service and/or information entry request formsIE₁ . . . IE_(n) (38) at the corresponding user interfaces I₁ . . .I_(n) (14). The completed service and/or information entry request formsIF₁ . . . IF_(n) (230) are derived from the user inputs UI₁ . . . UI_(n)(25) having the corresponding user service and/or information requestsiq₁ . . . iq_(n) (27), which may be entered as values or alternaterequests thereinto the corresponding service and/or information entryrequest forms IE₁ . . . IE_(n) (38).

The user U₁ . . . U_(n) (12) may alternatively communicate the userservice and/or information requests iq₁ . . . iq_(n) (27) by enteringthe alternate request links QL₁₁ . . . QL_(na) (203) or the serverrequest links UL₁₁ . . . UL_(ns) (204) or the additional request linksSL₁₁ . . . SL_(nw) (71) into the service and/or information entryrequest form IE₁ . . . IE_(n) (38) or into the completed service and/orinformation request form IF₁ . . . IF_(n) (230).

The server PS (18) and/or the C_(n) (16) may alternatively and/oradditionally use information resident within the server PS (18) and/orthe client C_(n) (16), such as default information, and/or informationcommunicated from the user U_(n) (12) through the user interface I_(n)(14) to the client C_(n) (16) to make the requests Q_(n1) . . . Q_(nm)(29) of the servers S₁ . . . S_(z) (20), in accordance with thedesignation scheme which designates the ones of the servers S₁ . . .S_(z) (20) to be communicated with corresponding to the requests Q₁₁ . .. Q_(nm) (29) as the corresponding server designations S₁₁ . . . S_(nm)(30).

FIG. 87 is a schematic representation showing queries QQ_(n1) . . .QQ_(nm) (53) and corresponding server addresses AQ_(n1) . . . AQ_(nm)(54). FIGS. 88-91 show the schematic representation of FIG. 87 havingtypical values.

D. Optional Instructions

Typically, information within the optional instructions V₁₁ . . . V_(nv)(289), and/or the optional hidden instructions H₁₁ . . . H_(ni) (292),and/or the optional hidden information portion J_(n) (287) are used bythe server PS (18) and/or specific ones of the clients C₁ . . . C_(n)(16), but may also be used by the servers S₁ . . . S_(z) (20).

Now, in yet more detail, the user inputs UI₁ . . . UI_(n) (25) may haveone or more of the same and/or different optional instruction valuesVV₁₁ . . . VV_(nv) (202). The optional instruction values VV₁₁ . . .VV_(nv) (202) may typically have instructions, which may be used by theserver PS (18) and/or the clients C₁ . . . C_(n) (16), such as, forexample, as instructions on how to request, organize, present and/ordisplay, and/or retrieve services and/or information from the servers S₁. . . S_(z) (20) and/or other suitable instructions.

Typical information that may be incorporated into the optionalinstruction values VV_(n1) . . . VV_(nv) (202) may include, for example,Searches per Group 311 and Group 312, shown in FIGS. 5A, 5B, and 6-10for a particular one of the service and/or information entry requestforms IE_(n) (38) at the user interface I_(n) (14) shown in FIGS. 81-86.

The Searches per Group 311 is considered to be the number of the serverquery values QV_(n1) . . . QV_(nu) (200), associated with correspondingones of the server name values AV_(n1) . . . AV_(nu) (201),corresponding to the requests Q_(n1) . . . Q_(nm) (29) to make of theservers S₁ . . . S_(z) (20). The Group 312 is considered to be the groupof the server query values QV_(n1) . . . QV_(nu) (200) to communicate toones of the servers S₁ . . . S_(z) (20) associated with thecorresponding ones of the server name values AV_(n1) . . . AV_(nu)(201), in accordance with the designation scheme corresponding to thecorresponding ones of the server designations S_(n1) . . . S_(nm) (30),corresponding to the requests Q_(n1) . . . Q_(nm) (29).

Page 313, which includes certain service and/or information locationinformation, which may be incorporated into the requests Q_(n1) . . .Q_(nm) (29) to be made of the associated corresponding ones of theservers S₁ . . . S_(z) (20), in accordance with the designation schemecorresponding to the corresponding ones of the server designationsS_(n1) . . . S_(nm) (30), may also be typically incorporated into theoptional instruction values VV_(n1) . . . VV_(nv) (202).

Timeout per Search Engine 314, which is substantially the maximum timefor the server PS (18) and/or the particular client C_(n) (16) makingthe requests Q_(n1) . . . Q_(nm) (29) to wait for each of the responsesR_(n1) . . . R_(nm) (32) from certain ones of the servers S₁ . . . S_(z)(20), in accordance with the designation scheme which designates thecertain ones of the servers S₁ . . . S_(z) (20) to be communicated withcorresponding to the requests Q_(n1) . . . Q_(nm) (29) as thecorresponding server designations S_(n1) . . . S_(nm) (30), may also betypically incorporated into the optional instruction values VV_(n1) . .. VV_(nv) (202).

URL's per Search Engine 315, which is the number of links and/ordescriptions to be returned to the user interface I_(n) (14) from eachof the responses R_(n1) . . . R_(nm) (32), may also be typicallyincorporated into the optional instruction values VV_(n1) . . . VV_(nv)(202). Search Engine Results 316 and URL Details 317, each of whichdesignate different presentation and/or display schemes to be presentedat the user interface I_(n) (14), may also be typically incorporatedinto the optional instruction values VV_(n1) . . . VV_(nv) (202).

In those instance in which, for example, the service and/or informationentry request form IE_(n) (38) at the user interface I_(n) (14) has onlyone entry field for one of the requests Q_(n1) (29), as in FIGS. 6, 8,and 10, and the optional instruction values VV₁₁ . . . V_(nv) (202) arenot visible, the server PS (18) and/or the particular client C_(n) (16)may then have default values resident therein for the Searches per Group311, and/or the Group 312, and/or the Page 313, and/or the Timeout perSearch Engine 314, and/or the URL's per Search Engine 315, and/or theSearch Engine Results 316, and/or the URL Details 317, and/or othersuitable ones of the optional instruction values VV₁₁ . . . V_(nv)(202), and/or the server PS (18) and/or the particular client C_(n) (16)may establish the default values, and/or the default values may beincorporated into the optional hidden instruction values Vv_(n1) . . .Vv_(ni) (276).

The server PS (18) and/or the particular client C_(n) (16) may make therequests Q_(n1) . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20),according to the designation scheme corresponding to the correspondingones of the server designations S_(n1) . . . S_(nm) (30), and theoptional instruction values VV_(n1) . . . VV_(nv) (202), typicallyhaving the Searches per Group 311, and/or the Group 312, and/or the Page313, and/or the Timeout per Search Engine 314, and/or the URL's perSearch Engine 315, and/or the Search Engine Results 316, and/or the URLDetails 317, and/or the default values which may be established or beresident within the server PS (18) and/or the particular client C_(n)(16), and/or the optional hidden instruction values Vv_(n1) . . .Vv_(ni) (276), and/or other information incorporated into the hiddenclient request elements HP_(n1) . . . HP_(nh) (256) hidden from the userU_(n) (12).

E. Communicating the Service and/or Information Requests

Now, each of the users U₁ . . . U_(n) (12) communicate the correspondinguser service and/or information requests iq₁ . . . iq_(n) (27) throughthe corresponding user interfaces I₁ . . . I_(n) (14) to thecorresponding clients C₁ . . . C_(n) (16), which optionally format thecorresponding user service and/or information requests iq₁ . . . iq_(n)(27) into the corresponding service and/or information requests IQ₁ . .. IQ_(n) (28). The clients C₁ . . . C_(n) (16) communicate thecorresponding service and/or information requests IQ₁ . . . IQ_(n) (28)to the server PS (18) and/or use the corresponding user service and/orinformation requests iq₁ . . . iq_(n) (27) internally to formulate therequests Q₁₁ . . . Q_(nm) (29).

F. Parsing, Processing, and/or Formatting the Service and/or InformationRequests

The server PS (18) and/or the clients C₁ . . . C_(n) (16) parse,process, and/or format the service and/or information requests IQ₁ . . .IQ_(n) (28) into the requests Q₁₁ . . . Q_(nm) (29), the optionalinstructions VJ₁₁ . . . VJ_(nk) (52), and information to openconnections OC₁₁ . . . OC_(nm) (323). FIG. 92 shows a particular one ofthe requests Q_(nm) (29), the optional instructions VJ_(n1) . . .VJ_(nk) (52), and the information to open connections OC₁₁ . . . OC_(nm)(323), which may be parsed, processed, and/or formatted from aparticular one of the service and/or information requests IQ_(n) (28).The clients C₁ . . . C_(n) (16) may alternatively and/or additionallyparse, process, and/or format the user service and/or informationrequests iq₁ . . . iq_(n) (27) directly into the requests Q₁₁ . . .Q_(nm) (29), and/or the optional instructions VJ₁₁ . . . VJ_(nk) (52)and the information required to open the connections OC₁₁ . . . OC_(nm)(323), as required.

Upon receipt of the service and/or information requests IQ₁ . . . IQ_(n)(28) at the server PS (18), communicated from the clients C₁ . . . C_(n)(16), the server PS (18) parses, processes, and/or formats each of thecorresponding service and/or information requests IQ₁ . . . IQ_(n) (28)into the corresponding queries QQ₁₁ . . . QQ_(nm) (53) and thecorresponding server addresses AQ₁₁ . . . AQ_(nm) (54) to openconnections OC₁₁ . . . OC_(nm) (323) with and make the requests Q₁₁ . .. Q_(nm) (29) of the servers S₁ . . . S_(z) (20), in accordance with thedesignation scheme which designates the certain ones of the servers S₁ .. . S_(z) (20) to be communicated with corresponding to the requests Q₁₁. . . Q_(nm) (29), and/or the optional instructions VJ₁₁ . . . VJ_(nk)(52) to be used by the server PS (18) in making the requests Q₁₁ . . .Q_(nm) (29) and/or in processing, formatting, grouping, and organizingthe responses R₁₁ . . . R_(nm) (32) from the ones of the servers S₁ . .. S_(z) (20) corresponding to the server designations S₁₁ . . . S_(nm)(30), and/or the additional optional responses RA₁₁ . . . RA_(nm) (40),into the corresponding service and/or information responses IR₁ . . .IR_(n) (34), as shown in FIG. 92.

Alternatively and/or additionally, upon receipt of the user serviceand/or information requests iq₁ . . . iq_(n) (27) at the correspondingclients C₁ . . . C_(n) (16), the corresponding clients C₁ . . . C_(n)(16) may parse, process, and/or format each of the user service and/orinformation requests iq₁ . . . iq_(n) (27) into corresponding queriesQQ₁₁ . . . QQ_(nm) (53) and corresponding server addresses AQ₁₁ . . .AQ_(nm) (54) to open connections OC₁₁ . . . OC_(nm) (323) with and makethe requests Q₁₁ . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20),in accordance with the designation scheme which designates the certainones of the servers S₁ . . . S_(z) (20) to be communicated withcorresponding to the requests Q₁₁ . . . Q_(nm) (29), and/or the optionalinstructions VJ₁₁ . . . VJ_(nk) (52) to be used by the correspondingclients C₁ . . . C_(n) (16) in making the requests Q₁₁ . . . Q_(nm) (29)and/or in processing, formatting, grouping, and organizing the responsesR₁₁ . . . R_(nm) (32) from the ones of the servers S₁ . . . S_(z) (20)corresponding to the server designations S₁₁ . . . S_(nm) (30), and/orthe additional optional responses RA₁₁ . . . RA_(nm) (40), into thecorresponding user service and/or information responses ir₁ . . . ir_(n)(36).

The server PS (18) parses, processes, and/or formats each of the serviceand/or information requests IQ₁ . . . IQ_(n) (28) into queries, serveraddresses to make the queries of, query groups and/or server groups, andinstructions to be used by the server PS (18), typically when the serverPS (18) makes the requests Q₁₁ . . . Q_(nm) (29) of the servers S₁ . . .S_(z) (20) corresponding to the server designations S₁₁ . . . S_(nm)(30) and/or the server PS (18) processes, formats, groups, and organizesthe responses R₁₁ . . . R_(nm) (32) from the ones of the servers S₁ . .. S_(z) (20) corresponding to the server designations S₁₁ . . . S_(nm)(30) at the server PS (18). Otherwise, the clients C₁ . . . C_(n) (16)may parse, process, and/or format each of the user service and/orinformation requests iq₁ . . . iq_(n) (27) into queries, serveraddresses to make the queries of, query groups and/or server groups, andinstructions, typically when the clients C₁ . . . C_(n) (16) make therequests Q₁₁ . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20)corresponding to the server designations S₁₁ . . . S_(nm) (30) and/orthe clients C₁ . . . C_(n) (16) process, format, group, and organize theresponses R₁₁ . . . R_(nm) (32) from the ones of the servers S₁ . . .S_(z) (20) corresponding to the server designations S₁₁ . . . S_(nm)(30) at the corresponding clients C₁ . . . C_(n) (16). Choice as towhether the server PS (18) and/or the clients C₁ . . . C_(n) (16) makesthe requests Q₁₁ . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20)corresponding to the server designations S₁₁ . . . S_(nm) (30) and/orprocess, format, group, and organize the responses R₁₁ . . . R_(nm) (32)are dependent on processing capabilities of the server PS (18) and/orthe clients C₁ . . . C_(n) (16) and other factors.

Ones of the requests Q₁₁ . . . Q_(nm) (29) may require furtherformatting and/or processing by the server PS (18) and/or thecorresponding clients C₁ . . . C_(n) (16), and/or other ones of therequests Q₁₁ . . . Q_(nm) (29) may already be formatted in accordancewith requirements with respect to communications protocols, the serviceand/or information requests IQ₁ . . . IQ_(n) (28), the servers S₁ . . .S_(z) (20), and/or the optional servers SO₁ . . . SO_(p) (22), and/orthe server PS (18), and/or other requirements of the network 24 of theclient-server multitasking system 10. The server PS (18) and/or theclients C₁ . . . C_(n) (16) parse, process, and/or format the requestsQ₁₁ . . . Q_(nm) (29), as required.

G. Formulating the Requests

Each of the optional instructions VJ_(n1) . . . VJ_(nk) (52) istypically parsed, and/or processed, and/or formatted, and/or grouped,and/or organized into particular ones of the optional instructionsVJ_(n1) . . . VJ_(nk) (52) for use by the server PS (18) and/orparticular ones of the clients C₁ . . . C_(n) (16), a particular one ofthe clients C₁ . . . C_(n) (16) being designated as the client C_(n)(16).

Each of the alternate request links QL_(n1) . . . QL_(na) (203) and theadditional request links SL₁₁ . . . SL_(nw) (71) are also typicallyparsed, and/or processed, and/or formatted, and/or grouped, and/ororganized for use by the server PS (18) and/or particular ones of theclients C₁ . . . C_(n) (16), a particular one of the clients C₁ . . .C_(n) (16) being designated as the client C_(n) (16).

The alternate request links QL_(n1) . . . QL_(na) (203) allow the userU_(n) (12) to make the service and/or information request IQ₁ . . .IQ_(n) (28) with preconfigured optional default selections alreadyplaced in the service and/or information request IQ₁ . . . IQ_(n) (28)for the user U_(n) (12). The additional request links SL_(n1) . . .SL_(nw) (71) allow the user U_(n) (12) to make additional optionalselections, based upon information and/or services previously requestedby the user U_(n) (12).

Typical ones of the optional instructions VJ_(n1) . . . VJ_(nk) (52) andthe additional request links SL_(n1) . . . SL_(nw) (71) that may beparsed, processed, and/or formatted from the service and/or informationrequest IQ_(n) (28) and/or the user service and/or information requestiq_(n) (27) are shown in FIG. 96.

The requests Q₁₁ . . . Q_(nm) (29) may be made by the server PS (18)and/or the corresponding clients C₁ . . . C_(n) (16) of the associatedcorresponding ones of the servers S₁ . . . S_(z) (20), according to thedesignation scheme corresponding to the corresponding ones of the serverdesignations S₁₁ . . . S_(nm) (30), in accordance with the optionalinstructions VJ₁₁ . . . VJ_(nk) (52) and/or default values for theoptional instructions VJ₁₁ . . . VJ_(nk) (52) resident within the serverPS (18) and/or the corresponding clients C₁ . . . C_(n) (16).

The service and/or information responses IR₁ . . . IR_(n) (34) and/orthe corresponding user service and/or information responses ir₁ . . .ir_(n) (36) may be formulated by the server PS (18) and/or thecorresponding clients C₁ . . . C_(n) (16), in accordance with theoptional instructions VJ₁₁ . . . VJ_(nk) (52) and/or default values forthe optional instructions VJ₁₁ . . . VJ_(nk) (52) resident within theserver PS (18) and/or the corresponding clients C₁ . . . C_(n) (16).

The optional instructions VJ_(n1) . . . VJ_(nk) (52) and the additionalrequest links SL₁₁ . . . SL_(nw) (71) for a particular one of theservice and/or information requests IQ_(n) (28) may typically haveSearches per Group 326, and/or Group 327, and/or Page 328A and/or Page328B, and/or Timeout per Search Engine 329, and/or URL's per SearchEngine 330, and/or Search Engine Results 331A and/or Search Display331B, and/or URL Details 332A and/or Description and/or List 332B, asshown in FIG. 96. Default values may additionally and/or alternativelybe established or be resident for any and/or all of the optionalinstructions VJ₁₁ . . . VJ_(nk) (52) within the server PS (18) and/orthe clients C₁ . . . C_(n) (16).

The Searches per Group 326 are typically considered to be the number ofthe queries QQ_(n1) . . . QQ_(nm) (53) to make of the servers S₁ . . .S_(z) (20) at the corresponding server addresses AQ_(n1) . . . AQ_(nm)(54), in accordance with the designation scheme which designates thecertain ones of the servers S₁ . . . S_(z) (20) to make the requestsQ_(n1) . . . Q_(nm) (29) of as the corresponding ones of the serverdesignations S_(n1) . . . S_(nm) (30).

The Group 327 is considered to be the group of the queries QQ_(n1) . . .QQ_(nm) (53) to make of the servers S₁ . . . S_(z) (20) at thecorresponding server addresses AQ_(n1) . . . AQ_(nm) (54), in accordancewith the designation scheme which designates the certain ones of theservers S₁ . . . S_(z) (20) to make the requests Q_(n1) . . . Q_(nm)(29) of as the corresponding ones of the server designations S_(n1) . .. S_(nm) (30).

The Page 328A and the Page 328B have certain service and/or informationlocation information, which may be incorporated into the requests Q_(n1). . . Q_(nm) (29) to be made of the associated corresponding ones of theservers S₁ . . . S_(z) (20), at the corresponding server addressesAQ_(n1) . . . AQ_(nm) (54), in accordance with the designation schemecorresponding to the corresponding ones of the server designationsS_(n1) . . . S_(nm) (30).

The Timeout per Search Engine 329 is considered to be substantially themaximum time for the server PS (18) and/or the particular client C_(n)(16) making the requests Q_(n1) . . . Q_(nm) (29) to wait for each ofthe responses R_(n1) . . . R_(nm) (32) from certain ones of the serversS₁ . . . S_(z) (20), in accordance with the designation scheme whichdesignates the certain ones of the servers S₁ . . . S_(z) (20) to becommunicated with corresponding to the requests Q_(n1) . . . Q_(nm) (29)as the corresponding server designations S_(n1) . . . S_(nm) (30).

The URL's per Search Engine 330, is considered to be the number oflinks, and/or descriptions, and/or prices/values, and/or images to bereturned to the user interface I_(n) (14) from each of the responsesR_(n1) . . . R_(nm) (32).

The Search Engine Results 331A and the Search Display 331B eachdesignate presentation and/or display schemes to be presented at theuser interface I_(n) (14). The URL Details 332A and the Descriptionand/or List 332B each also designate presentation and/or display schemesto be presented at the user interface I_(n) (14).

FIG. 133 is a schematic representation of certain typical optionalinstructions VJ_(nm1) . . . VJ_(nk) (52) and/or certain additionalrequest links SL_(n1) . . . SL_(nw) (71), referred to as the SearchEngine Results 331A, which are shown to be Interleave 331A-1, Separate331A-2, Combine $[a-z] 331A-3, Combine $[z-a] 331A-4, Separate $[a-z]331A-5, Separate $[z-a] 331A-6, which are instructions for parsing,processing, sorting, and/or formatting the service and/or informationresponse IR_(n) (34).

FIG. 134 is a schematic representation of other certain typical optionalinstructions VJ_(nm1) . . . VJ_(nk) (52) and/or other certain additionalrequest links SL_(n1) . . . SL_(nw) (71), referred to as the URL Details332A, which are other instructions for parsing, processing, sorting,and/or formatting the service and/or information response IR_(n) (34) inSummary 332A-1 or List 332A-2 formats.

FIG. 135 depicts certain typical additional request links SL_(n1) . . .SL_(nw) (71), and also shows the Search Display 331B, which are shown tobe Interleave 331B-1, Separate 331B-2, Combine $[a-z] 331B-3, Combine$[z-a] 331B-4, Separate $[a-z] 331B-5, Separate $[z-a] 331B-6, which areinstructions for parsing, processing, sorting, and/or formatting theservice and/or information response IR_(n) (34) and the Descriptionand/or List 332B,which are other instructions for parsing, processing,sorting, and/or formatting the service and/or information responseIR_(n) (34) in Summary or List formats.

The optional instructions VJ_(n1) . . . VJ_(nk) (52) may also typicallyhave Next Group 333 and Previous Group 334, which are considered to bethe next group and the previous group, respectively, to make the queriesQQ_(n1) . . . QQ_(nm) (53) thereof at the next and previous ones of thecorresponding groups of the queries QQ_(n1) . . . QQ_(nm) (53) to makeof the servers S₁ . . . S_(z) (20) thereof at the corresponding serveraddresses AQ_(n1) . . . AQ_(nm) (54), in accordance with the designationscheme which designates the certain ones of the servers S₁ . . . S_(z)(20) to make the requests Q_(n1) . . . Q_(nm) (29) thereof as thecorresponding ones of the server designations S_(n1) . . . S_(nm) (30).Information about Current Group 337 having the queries QQ_(n1) . . .QQ_(nm) (53) and the server addresses AQ_(n1) . . . AQ_(nm) (54) is alsoshown. Current Page Number 338 is also indicated.

The optional instructions VJ_(n1) . . . VJ_(nk) (52) for a particularone of the service and/or information requests IQ_(n) (28) may alsotypically have Next Page 335 and Previous Page 336, each of which hascertain different service and/or information location information, whichmay be incorporated into the requests Q_(n1) . . . Q_(nm) (29) to bemade of the associated corresponding ones of the servers S₁ . . . S_(z)(20), in accordance with the designation scheme corresponding to thecorresponding ones of the server designations S_(n1) . . . S_(nm) (30).

H. Determining Queries and Servers to Make the Requests Thereof

The server PS (18) and/or the clients C₁ . . . C_(n) (16) evaluate theoptional instructions VJ₁₁ . . . VJ_(nk) (52), determine the queriesQQ₁₁ . . . QQ_(nm) (53) and the servers S₁ . . . S_(z) (20) to make therequests Q₁₁ . . . Q_(nm) (29) thereof at the corresponding serveraddresses AQ₁₁ . . . AQ_(nm) (54), in accordance with the designationscheme which designates the certain ones of the servers S₁ . . . S_(z)(20) to be communicated with as the server designations S₁₁ . . . S_(nm)(30), corresponding to the requests Q₁₁ . . . Q_(nm) (29), and group thequeries QQ₁₁ . . . QQ_(nm) (53) and the corresponding server addressesAQ₁₁ . . . AQ_(nm) (54) associated therewith.

FIG. 96 shows typical ones of the queries QQ_(n1) . . . QQ_(nm) (53),the corresponding server addresses AQ_(n1) . . . AQ_(nm) (54), and theoptional instructions VJ_(n1) . . . VJ_(nk) (52) that may be parsed,processed, and/or formatted from the service and/or information requestIQ_(n) (28) and/or the user service and/or information request iq_(n)(27).

The queries QQ₁₁ . . . QQ_(nm) (53) and the servers S₁ . . . S_(z) (20)to make the requests Q₁₁ . . . Q_(nm) (29) thereof are typically basedupon the values designated in and parsed from the queries QQ₁₁ . . .QQ_(nm) (53) and the values designated in and parsed from thecorresponding server addresses AQ₁₁ . . . AQ_(nm) (54), in accordancewith the designation scheme which designates the certain ones of theservers S₁ . . . S_(z) (20) to be communicated with as the serverdesignations S₁₁ . . . S_(nm) (30), corresponding to the requests Q₁₁ .. . Q_(nm) (29), and the Searches per Group 326, the Group 327, the Page328A and/or the Page 328B within the optional instructions VJ₁₁ . . .VJ_(nk) (52).

The server PS (18) and/or the clients C₁ . . . C_(n) (16) evaluate thevalues in the Group 327, the Searches per Group 326, the queries QQ₁₁ .. . QQ_(nm) (53), and the corresponding server addresses AQ₁₁ . . .AQ_(nm) (54), and determine the servers S₁ . . . S_(z) (20)corresponding to the corresponding server addresses AQ₁₁ . . . AQ_(nm)(54) within the Group 327, in accordance with the designation schemewhich designates the certain ones of the servers S₁ . . . S_(z) (20) tobe communicated with as the server designations S₁₁ . . . S_(nm) (30) tomake the requests Q₁₁ . . . Q_(nm) (29) thereof, and the Page 328Aand/or the Page 328B.

The Group 327 and the Searches per Group 326 are used to determine whichof the servers S₁ . . . S_(z) (20) to make the requests Q₁₁ . . . Q_(nm)(29) thereof.

The server PS (18) and/or the clients C₁ . . . C_(n) (16) determine thesize of the Group 327 from the Searches per Group 326 and the Group 327,and the servers S₁ . . . S_(z) (20) associated with the correspondingserver addresses AQ₁₁ . . . AQ_(nm) (54) within the Group 327, inaccordance with the designation scheme which designates the certain onesof the servers S₁ . . . S_(z) (20) to be communicated with as the serverdesignations S₁₁ . . . S_(nm) (30).

The Searches per Group 326 and the Group 327 are used to formulate thecurrent request groups QA_(1c) . . . Q_(nc) (50) having thecorresponding queries QQ₁₁ . . . QQ_(nm) (53) and the correspondingserver addresses AQ₁₁ . . . AQ_(nm) (54) to open connections with andmake the requests Q₁₁ . . . Q_(nm) (29) of the servers S₁ . . . S_(z)(20), in accordance with the designation scheme which designates thecertain ones of the servers S₁ . . . S_(z) (20) to be communicated withcorresponding to the requests Q₁₁ . . . Q_(nm) (29) thereof as theserver designations S₁₁ . . . S_(nm) (30), corresponding to the requestsQ₁₁ . . . Q_(nm) (29), for corresponding ones of the service and/orinformation requests IQ₁ . . . IQ_(n) (28) and/or the user serviceand/or information requests iq₁ . . . iq_(n) (27).

The queries QQ₁₁ . . . QQ_(nm) (53), the server addresses AQ₁₁ . . .AQ_(nm) (54), and the Page 328A and/or the Page 328B provide thelocation of information and/or services to the server PS (18) and/or theclients C₁ . . . C_(n) (16) within the Group 327, in accordance with theSearches per Group 326, to make the requests Q₁₁ . . . Q_(nm) (29)thereof, in accordance with the designation scheme which designates theones of the servers S₁ . . . S_(z) (20) to make the requests Q₁₁ . . .Q_(nm) (29) thereof as the server designations S₁₁ . . . S_(nm) (30),corresponding to the requests Q₁₁ . . . Q_(nm) (29).

The URL's per Search Engine 330 determine whether the server PS (18)and/or the clients C₁ . . . C_(n) (16) communicate additional ones ofthe requests Q₁₁ . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20),depending upon the number of the links, and/or descriptions, and/orprices/values, and/or images requested by ones of the user U₁ . . .U_(n) (12) to be returned to the user interfaces I₁ . . . I_(n) (14),and the number of links, and/or descriptions, and/or prices/values,and/or images available within each of the corresponding ones of theresponses R₁₁ . . . R_(nm) (32). If insufficient ones of the links,and/or descriptions, and/or prices/values, and/or images are notavailable within the responses R₁₁ . . . R_(nm) (32) to satisfy deliveryof the number of the URL's per Search Engine 330 requested by certainones the users U₁ . . . U_(n) (12), the server PS (18) and/or theclients C₁ . . . C_(n) (16) may yet make additional ones of the requestsQ₁₁ . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20), in orderdeliver the number of the links, and/or descriptions, and/orprices/values, and/or images requested in the number of the URL's perSearch Engine 330 to the user interfaces I₁ . . . I_(n) (14) requestedby certain ones of the user U₁ . . . U_(n) (12).

If the optional instructions do not indicate which ones of the serversS₁ . . . S_(z) (20) to make the requests Q₁₁ . . . Q_(nm) (29) thereof,in accordance with the designation scheme which designates the certainones of the servers S₁ . . . S_(z) (20) to be communicated with as theserver designations S₁₁ . . . S_(nm) (30), corresponding to the requestsQ₁₁ . . . Q_(nm) (29), default values may be used. The default valuesmay be resident within the server PS (18) and/or the clients C₁ . . .C_(n) (16).

If all and/or a portion of the optional instructions VJ₁₁ . . . VJ_(nk)(52) are absent and/or are not communicated to the server PS (18) and/orthe clients C₁ . . . C_(n) (16), default values may be used. The defaultvalues may be resident within the server PS (18) and/or the clients C₁ .. . C_(n) (16).

I. Grouping the Queries and Sorting/Grouping Criteria

Upon receipt of the service and/or information requests IQ₁ . . . IQ_(n)(28) at the server PS (18), communicated from the corresponding clientsC₁ . . . C_(n) (16), the server PS (18) parses, processes, and/orformats each of the service and/or information requests IQ₁ . . . IQ_(n)(28) into the corresponding current request groups QA_(1c) . . . QA_(nc)(50) having the corresponding queries QQ₁₁ . . . QQ_(nm) (53) and thecorresponding server addresses AQ₁₁ . . . AQ_(nm) (54) to openconnections with and make the requests Q₁₁ . . . Q_(nm) (29) of theservers S₁ . . . S_(z) (20), in accordance with the designation schemewhich designates the certain ones of the servers S₁ . . . S_(z) (20) tobe communicated with corresponding to the requests Q₁₁ . . . Q_(nm) (29)as the corresponding server designations S₁₁ . . . S_(nm) (30), shownfor a particular one of the service and/or information requests IQ_(n)(28) in FIG. 59. The process 104 of deriving the service and/orinformation response IR_(n) (34) for the grouping and/or sortingcriteria of FIG. 59 is shown in FIG. 71.

The server PS (18) also parses, processes, and/or formats each of theservice and/or information requests IQ₁ . . . IQ_(n) (28) into thecorresponding request groups QA₁₁ . . . QA_(nz) (51) having thecorresponding other queries QQ_(1a) . . . QQ_(nz) (55) and thecorresponding other server addresses AQ_(1a) . . . AQ_(nz) (56), and thecorresponding optional instructions VJ₁₁ . . . VJ_(nk) (52), also shownfor a particular one of the service and/or information requests IQ_(n)(28) in FIG. 59.

Certain ones of the clients C₁ . . . C_(n) (16) may alternatively and/oradditionally make the requests Q₁₁ . . . Q_(nm) (29) of the servers S₁ .. . S_(z) (20), in accordance with the designation scheme whichdesignates the certain ones of the servers S₁ . . . S_(z) (20) to becommunicated with corresponding to the requests Q₁₁ . . . Q_(nm) (29) asthe corresponding server designations S₁₁ . . . S_(nm) (30), andformulate the corresponding user service and/or information response ir₁. . . ir_(n) (36), as previously described, as shown in FIG. 63. Theprocess 104 of deriving the user service and/or information responseir_(n) (36) for the grouping and/or sorting criteria of FIG. 59 is shownin FIG. 71.

Upon receipt of the user service and/or information requests iq₁ . . .iq_(n) (27) at the corresponding clients C₁ . . . C_(n) (16), certainones of the corresponding clients C₁ . . . C_(n) (16) may parse,process, and/or format the corresponding user service and/or informationrequests iq₁ . . . iq_(n) (27) into the corresponding current requestgroups QA_(1c) . . . QA_(nc) (50) having the corresponding queries QQ₁₁. . . QQ_(nm) (53) and the corresponding server addresses AQ₁₁ . . .AQ_(nm) (54) to open connections with and make the requests Q₁₁ . . .Q_(nm) (29) of the servers S₁ . . . S_(z) (20), in accordance with thedesignation scheme which designates the certain ones of the servers S₁ .. . S_(z) (20) to be communicated with corresponding to the requests Q₁₁. . . Q_(nm) (29), shown for a particular one of the user service and/orinformation requests iq_(n) (27) in FIG. 63. The corresponding clientsC₁ . . . C_(n) (16) may also parse, process, and/or format thecorresponding user service and/or information response ir₁ . . . ir_(n)(36) into the corresponding request groups QA₁₁ . . . Q_(nz) (51) havingthe corresponding other queries QQ_(1a) . . . QQ_(nz) (55) and thecorresponding other server addresses AQ_(1a) . . . AQ_(nz) (56), and thecorresponding optional instructions VJ₁₁ . . . VJ_(nk) (52), also shownfor a particular one of the user service and/or information requestsiq_(n) (27) in FIG. 63.

The server PS (18) makes the requests Q₁₁ . . . Q_(nm) (29) of theservers S₁ . . . S_(z) (20), in accordance with the designation schemewhich designates the certain ones of the servers S₁ . . . S_(z) (20) tobe communicated with corresponding to the requests Q₁₁ . . . Q_(nm) (29)as the corresponding server designations S₁₁ . . . S_(nm) (30), as shownin FIG. 59, and certain ones of the clients C₁ . . . C_(n) (16) mayadditionally and/or alternatively make the requests Q₁₁ . . . Q_(nm)(29) of the servers S₁ . . . S_(z) (20), in accordance with thedesignation scheme which designates the certain ones of the servers S₁ .. . S_(z) (20) to be communicated with corresponding to the requests Q₁₁. . . Q_(nm) (29) as the corresponding server designations S₁₁ . . .S_(nm) (30), as shown in FIG. 63.

The Searches per Group 326 and the Group 327 are used to formulate thecurrent request group QA_(nc) (50) having the corresponding queriesQQ_(n1) . . . QQ_(nm) (53) and the corresponding server addressesAQ_(n1) . . . AQ_(nm) (54) to open connections with and make therequests Q_(n1) . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20), inaccordance with the designation scheme which designates the certain onesof the servers S₁ . . . S_(z) (20) to be communicated with correspondingto the requests Q_(n1) . . . Q_(nm) (29) thereof as the serverdesignations S₁₁ . . . S_(nm) (30), corresponding to the requests Q₁₁ .. . Q_(nm) (29), for the service and/or information request IQ_(n) (28)and/or the user service and/or information request iq_(n) (27).

Information from the current request group QA_(nc) (50) having thecorresponding queries QQ_(n1) . . . QQ_(nm) (53) and the correspondingserver addresses AQ_(n1) . . . AQ_(nm) (54) is formulated into thecorresponding request pointer/address group QZ_(n) (60) having thepointers/addresses PG_(n1) . . . PG_(nz) (61) associated therewith, asshown in FIGS. 59 and 63.

Each of the pointers/addresses PG_(n1) . . . PG_(nz) (61) are directedto point/address the corresponding addressable query pointer/addressgroups QG_(n1) . . . QG_(nz) (62) associated therewith, which aid inobtaining services and/or information from the certain ones of theaddressable response information groups RG_(n1) . . . RG_(nm) (57) to beincorporated into the query information groups GI_(n1) . . . GI_(nz)(63).

Ones of the addressable query information groups GI_(n1) . . . GI_(nz)(63) may be associated with corresponding ones of the addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62).

Each of the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) associated with the service and/or information requestIQ_(n). has the pointers/addresses PP_(n11) . . . PP_(nmr) (64) directedto address/point services and/or information in the addressable responseinformation groups RG_(n1) . . . RG_(nm) (57), based upon the groupingand/or sorting criteria.

Information and/or services in the addressable response informationgroups RG_(n1) . . . RG_(nm) (57) is addressed with thepointers/addresses PP_(n11) . . . PP_(nmr) (64) from the querypointer/address groups QG_(n1) . . . QG_(nz) (62), and informationand/or services from the addressable response information groups RG_(n1). . . RG_(nm) (57) is incorporated into the addressable queryinformation groups GI_(n1) . . . GI_(nz) (63) corresponding to thepointers/addresses PP_(n11) . . . PP_(nmr) (64), which are formulated bythe addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62),in accordance with the grouping and/or sorting criteria.

FIGS. 59 and 63 show the request pointer/address group QZ_(n) (60), theaddressable query pointer/address groups QG_(n1) . . . QG_(nz) (62), thepointers/addresses PP_(n11) . . . PP_(nmr) (64), associated ones of theaddressable response information groups RG_(n1) . . . RG_(nm) (57), andthe query information group GI_(nz) (63) associated with the querypointer/address group QG_(nz) (62). FIGS. 59 and 63 show the rthpointers/addresses PP_(n1r) . . . PP_(nmr) (64), which point to the rthoptional addressable pointer/address indices IN_(nmr) . . . IN_(nmr)(81) of the corresponding rth individual information groups LG_(n1r) . .. LG_(nmr) (80) of the addressable response information groups RG_(n1) .. . RG_(nm) (57) associated with the query pointer/address group QG_(nz)(62) and the associated query information group GI_(nz) (63).

FIG. 97 shows the request pointer/address group QZ_(n) (60), aparticular one of the addressable query pointer/address groups QG_(n1) .. . QG_(nz) (62), designated as the query pointer/address group QG_(nz)(62), the pointers/addresses PP_(n11) . . . PP_(nmr) (64), associatedones of the addressable response information groups RG_(n1) . . .RG_(nm) (57), and the query information group GI_(nz) (63) associatedwith the query pointer/address group QG_(nz) (62).

The addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62)each have corresponding ones of query information groups GI_(n1) . . .GI_(nz) (63) associated therewith. Each of the query information groupsGI_(n1) . . . GI_(nz) (63) have information and/or services therein,which are derived from information and/or services obtained from thecertain ones of the addressable response information groups RG_(n1) . .. RG_(nm) (57), which are addressed to provide such information with theaid of the corresponding pointers/addresses PP_(n11) . . . PP_(nmr)(64). Each of the pointers/addresses PP_(n11) . . . PP_(nmr) (64) aredirected to point/address information and/or services in thecorresponding response information groups RG_(n1) . . . RG_(nm) (57)associated therewith, which the information and/or services incorporatedinto the ones of the query information groups GI_(n1) . . . GI_(nz) (63)associated with the corresponding addressable query pointer/addressgroups QG_(n1) . . . QG_(nz) (62) is obtained therefrom.

The addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62)may be used to aid in formulating the query information groups GI_(n1) .. . GI_(nz) (63), having information obtained from the addressableresponse information groups RG_(nm) (57), resulting from certain ones ofthe queries QQ_(n1) . . . QQ_(nm) (53) grouped one with the other and/orthe associated ones of the corresponding server addresses AQ_(n1) . . .AQ_(nm) (54). The query information groups GI_(n1) . . . GI_(nz) (63)may be presented to the user U_(n) (12) through the user interface I_(n)(14). The addressable query pointer/address groups QG_(n1) . . . QG_(nz)(62) may be derived from query criteria in the optional instructionsVJ₁₁ . . . VJ_(nk) (52) and/or using default criteria resident withinthe server PS (18) and/or the client C_(n) (16).

Query grouping criteria giving the user U_(n) (12) the ability toformulate the addressable query pointer/address groups QG_(n1) . . .QG_(nz) (62) may be incorporated into the optional instructions VJ₁₁ . .. VJ_(nk) (52), which may be entered into the user interface I_(n) (14)through the user input UI_(n) (25) by the user U_(n) (12). Typically,however, the queries QQ_(n1) . . . QQ_(nm) (53) having the same and/orsubstantially the same values are grouped one with the other inindividual ones of the addressable query pointer/address groups QG_(n1). . . QG_(nz) (62). Default criteria may be resident within the serverPS (18) and/or the client C_(n) (16).

The size of the request pointer/address group QZ_(n) (60) and whichparticular ones of the queries QQ_(n1) . . . QQ_(nm) (53) and thecorresponding ones of the server addresses AQ_(n1) . . . AQ_(nm) (54) touse in the requests Q_(n1) . . . Q_(nm) (29), and thus constructionand/or formulation of the addressable query pointer/address groupsQG_(n1) . . . QG_(nz) (62) to incorporate into the particular requestpointer/address group QZ_(n) (60), and, thus, delivery of information inthe query information groups GI_(n1) . . . GI_(nz) (63) is determined bythe current request groups QA_(1c) . . . QA_(nc) (50), which may bedetermined from the Group 327 and the Searches per Group 326, thequeries QQ_(n1) . . . QQ_(nm) (53) and the corresponding ones of theserver addresses AQ_(n1) . . . AQ_(nm) (54) therein.

Certain ones of the queries QQ_(n1) . . . QQ_(nm) (53) may be groupedone with the other in the addressable query pointer/address groupsQG_(n1) . . . QG_(nz) (62), which have the certain ones of the queriesQQ_(n1) . . . QQ_(nm) (53) and the corresponding ones of the serveraddresses AQ_(n1) . . . AQ_(nm) (54) associated therewith, and thecorresponding pointers/addresses PP_(n11) . . . PP_(nmr) (64) associatedwith the certain ones of the queries QQ_(n1) . . . QQ_(nm) (53), thecorresponding ones of the server addresses AQ_(n1) . . . AQ_(nm) (54),and certain ones of response information groups RG_(n1) . . . RG_(nm)(57).

Typical sorting and/or grouping criteria, for example, may group certainones of the queries QQ_(n1) . . . QQ_(nm) (53) having the same and/orsubstantially the same values grouped in a particular one of the queryinformation groups GI_(nz) . . . GI_(nz) (63), designated as the queryinformation group GI_(nz) (63), as shown in FIG. 98 and in certain onesof FIGS. 27A-52C, inclusive.

Alternatively and/or additionally, other typical sorting and/or groupingcriteria, for example, may group certain ones of the server addressesAQ_(n1) . . . AQ_(nm) (54), having the same and/or substantially thesame values grouped in a particular one of the query information groupsGI_(nz) . . . GI_(nz) (63), designated as the query information groupGI_(nz) (63), as shown in FIG. 99.

FIGS. 97-99 show the rth pointers/addresses PP_(ner) (64), PP_(nrr)(64), and PP_(nwr) (64), which point to the rth optional addressablepointer/address indices IN_(ner) (81), IN_(nrr) (81), and IN_(nwr) (81)of the corresponding rth individual information groups LG_(ner) (80),LG_(nrr) (80), and LG_(nwr) (80) of the addressable response informationgroups RG_(ne) (57), RG_(nr) (57), and RG_(nw) (57) associated with thequery pointer/address group QG_(nz) (62) and the associated queryinformation group GI_(nz) (63).

Alternatively and/or additionally, the user U_(n) (12) may select querygrouping criteria, which simply provides information to the userinterface I_(n) (14), separately with respect to the individual serveraddresses AQ_(n1) . . . AQ_(nm) (54), as shown in FIGS. 60 and 64 and incertain ones of FIGS. 27A-52C, inclusive. For example, the queryinformation groups GI_(n1) . . . GI_(nz) (63), may alternatively and/oradditionally be correspondingly associated with the server addressAQ_(n1) . . . AQ_(nm) (54), and, thus, may be correspondingly associatedwith the addressable response information groups RG_(n1) . . . RG_(nm)(57). The query information group GI_(n1) (63) may, thus, be associatedwith the server address AQ_(n1) (54), the addressable responseinformation group RG_(n1) (57), and the query information group GI_(n1)(63); the query information group GI_(n2) (63) may, thus, be associatedwith the server address AQ_(n2) (54), the addressable responseinformation group RG_(n2) (57), and the query information group GI_(n2)(63), and so on; and the query information group GI_(nz) (63) may, thus,be associated with the server address AQ_(nz) (54), the addressableresponse information group RG_(n2) (57), and the query information groupGI_(nz) (63), as shown in FIGS. 60 and 64. The process 104 of derivingthe service and/or information response IR_(n) (34) and/or the userservice and/or information response ir_(n) (36) for the grouping and/orsorting criteria of FIGS. 60 and 64 is shown in FIG. 72.

The pointing/addressing scheme of FIGS. 60 and 64 is, of course, a muchsimpler pointing/addressing scheme than the pointing/addressing schemeof FIGS. 59 and 63, and does not require incorporating the addressablequery pointer/address groups QG_(n1) . . . QG_(nz) (62) into the requestpointer/address group QZ_(n) (60). Each of the pointers/addressesPF_(n11) . . . PF_(nmr) (69), of FIGS. 60 and 64, may then be directedto point/address the corresponding response information groups RG_(n1) .. . RG_(nm) (57) directly from the request pointer/address group QY_(ns)(68), to obtain information from the corresponding response informationgroups RG_(n1) . . . RG_(nm) (57) and incorporation into correspondingones of the corresponding query information groups GI_(n1) . . . GI_(nz)(63), as shown in FIGS. 60 and 64. In this case, the addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62) may be bypassed and/oreliminated completely, thus simplifying the process. Of course, then, inthis case, the resulting sorting and grouping is not as sophisticated,and allows for such simplification.

The above sorting criteria addressing schemes are meant only as typicalexamples of sorting criteria addressing schemes that may be used. Yetother sorting criteria addressing schemes and/or combinations thereofmay be used.

FIG. 100 shows typical ones of the addressable query pointer/addressgroups QG_(n1) . . . QG_(nz) (62) having the typical ones of the queriesQQ_(n1) . . . QQ_(nm) (53), the typical ones of the server addressesAQ_(n1) . . . AQ_(nm) (54), and the corresponding ones of typical onesof the pointers/addresses PP_(n11) . . . PP_(nmr) (64) having the sameones of the queries QQ_(n1) . . . QQ_(nm) (53) grouped one with theother in individual ones of the addressable query pointer/address groupsQG_(n1) . . . QG_(nz) (62).

More particularly, FIG. 100 shows the query pointer/address groupQG_(n1) (62), the query pointer/address group QG_(n2) (62), and thequery pointer/address group QG_(n3) (62). The query pointer/addressgroup QG_(n1) (62) of FIG. 100 has the same ones of the queries QQ_(n1)(53), QQ_(n2) (53), QQ_(n3) (53), and QQ_(n9) (53), the ones of theserver addresses AQ_(n1) (54), AQ_(n2) (54), AQ_(n3) (54), and AQ_(n9)(54), and the ones of the pointers/addresses PP_(n1r) (64), PP_(n2r)(64), PP_(n3r) (64), and PP_(n9r) (64) associated therewith. The querypointer/address group QG_(n2) (62) of FIG. 100 has the same ones of thequeries QQ_(n4) (53) and QQ_(n7) (53), the ones of the server addressesAQ_(n4) (54) and AQ_(n7) (54) the ones of the pointer/addresses PP_(n4r)(64) and PP_(n7r) (64) associated therewith. The query pointer/addressgroup QG_(n3) (62) of FIG. 100 has the same ones of the query valuesQQ_(n5) (53), QQ_(n6) (53), and QQ_(n8) (53), the ones of the serveraddresses AQ_(n5) (54), AQ_(n6) (54), and AQ_(n8) (54) and the ones ofthe pointers/addresses PP_(n5r) (64), PP_(n6r) (64), and PP_(n8r) (64)associated therewith.

The addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62),however, may alternatively and/or additionally be grouped, for example,by the server addresses AQ_(n1) . . . AQ_(nm) (54) and have thecorresponding query values QQ_(n1) . . . QQ_(nm) (53) associatedtherewith. Ones of the same and/or substantially the same ones of theserver addresses AQ_(n1) . . . AQ_(nm) (54), for example, having thecorresponding queries QQ_(n1) . . . QQ_(nm) (53) associated therewithmay be used as the grouping criteria.

FIG. 101 shows another schematic representation of the typical ones ofthe addressable query pointer/address groups QG_(n1) . . . QG_(nz) (62)having the typical ones of the queries QQ_(n1) . . . QQ_(nm) (53), thetypical ones of the server addresses AQ_(n1) . . . AQ_(nm) (54), and thetypical the ones of the pointer/addresses PP_(n11) . . . PP_(nmr) (64)of FIG. 100 associated therewith.

FIG. 102 is a generic schematic representation of the addressable querypointer/address groups QG_(n1) . . . QG_(nz) (62) having the queriesQQ_(n1) . . . QQ_(nm) (53), the server addresses AQ_(n1) . . . AQ_(nm)(54), and the pointers/addresses PP_(n11) . . . PP_(nmr) (64) associatedtherewith.

Certain information in the addressable response information groupsRG_(n1) . . . RG_(nm) (57) may be associated with the correspondingqueries QQ_(n1) . . . QQ_(nm) (53) and/or the corresponding serveraddresses AQ_(n1) . . . AQ_(nm) (54) within the current request groupQA_(nc) (50), and may optionally be used by the server PS (18) and/orthe client C_(n) (16).

Certain information in the addressable response information groupsRG_(n1) . . . RG_(nm) (57) may also be incorporated into the optionalinstructions VJ_(n1) . . . VJ_(nk) (52). Such information may beincorporated into the optional instructions VJ_(n1) . . . VJ_(nk) (52)and/or may also be additionally and/or alternatively optionally residentwithin the server PS (18) and/or the client C_(n) (16).

J. Communicating the Requests to the Servers

The server PS (18) and/or the clients C₁ . . . C_(n) (16) contact andopen the connections OC₁₁ . . . OC_(nm) (323) with ones of the serversS₁ . . . S_(z) (20), according to the server designations S₁₁ . . .S_(nm) (30) at the corresponding server addresses A₁₁ . . . A_(nu) (265)at corresponding ports W₁₁ . . . W_(nm) (343). The server PS (18) and/orthe clients C₁ . . . C_(n) (16) communicate the requests Q₁₁ . . .Q_(nm) (29) of one or more of the same and/or different ones of theservers S₁ . . . S_(z) (20), designated within the Group 327 and theSearches per Group 326 to make the requests Q₁₁ . . . Q_(nm) (29)thereof, in accordance with the designation scheme corresponding to thecorresponding ones of the server designations S₁₁ . . . S_(nm) (30),corresponding to the requests Q₁₁ . . . Q_(nm) (29). If the Group 327 isnot specified and/or the Searches per Group 326 are not specified by theusers U₁ . . . U_(n) (12), default values may additionally and/oralternatively values be used.

A particular one of the requests Q₁₁ . . . Q_(nm) (29), hereinafterdesignated as the request Q_(nm) (29), corresponding to one requestwithin the requests Q_(n1) . . . Q_(nm) (29) corresponding to the userU_(n) (12), is shown schematically in FIG. 103.

Information 344 that may be used for formulating a typical particularone of the requests Q_(nm) (29) from the service and/or informationrequest IQ_(n) (28), and parsing, processing, and/or formatting theoptional instructions VJ_(n1) . . . VJ_(nk) (52), and opening theconnection OC_(nm) (323) is shown in FIGS. 92-95.

Now, in more detail, the request Q_(nm) (29) may have a correspondingrequest line L_(nm) (345), corresponding optional request header fieldsJH_(n1) . . . JH_(ns) (346), and a corresponding optional entity bodyEH_(nm) (347). The request line L_(nm) (345) may have a correspondingmethod M_(nm) (348), a corresponding target resource P_(nm) (349), whichmay have information associated with the corresponding query QQ_(nm)(53), and corresponding protocol B_(nm) (350).

The user U_(n) (12), the server PS (18) and/or the client C_(n) (16) mayoptionally specify the port W_(nm) (343) to communicate the requestQ_(nm) (29) therethrough, and/or the method M_(nm) (348), and/or theprotocol B_(nm) (350). The port W_(nm) (343), and/or the method M_(nm)(348), and/or the protocol B_(nm) (350) may optionally be residentwithin the server PS (18) and/or the client C_(n) (16). Default valuesmay also be used for the port W_(nm) (343) and/or the protocol B_(nm)(350).

Typically, information within or from any and/or all or a portion of thequeries QQ_(nm) (53) may be incorporated into the corresponding ones ofthe target resources P₁₁ . . . P_(nm) (349) and/or the correspondingones of the optional entity bodies EH₁₁ . . . EH_(nm) (347), and may incertain instances depend upon the method M₁₁ . . . M_(nm) (348).

However, information that may be used for opening the connections OC₁₁ .. . OC_(nm) (323) and formulating the requests Q₁₁ . . . Q_(nm) (29)from the service and/or information requests IQ₁ . . . IQ_(n) (28) maybe derived from any and/or all or a portion of the user client requestsQC₁₁ . . . QC_(nu) (280) accessible to the users U₁ . . . U_(n) (12)and/or the hidden client requests HC_(n1) . . . HC_(nh) (281) hiddenfrom the users U₁ . . . U_(n) (12), and/or a combination thereof, and/ormay also have information and/or instructions to be utilized by theserver PS (18) and/or ones of the clients C₁ . . . C_(n) (16).

Alternatively information from the alternate request links QL₁₁ . . .QL_(na) (203), and/or the server request links UL₁₁ . . . UL_(ns) (204),and/or the additional request links SL₁₁ . . . SL_(nw) (71), and/or acombination thereof, may be used by the server PS (18) and/or ones ofthe clients C₁ . . . C_(n) (16) to formulate the requests Q₁₁ . . .Q_(nm) (29).

There may be m different or same ones of the requests Q_(n1) . . .Q_(nm) (29) from the client C_(n) (16) at any time, and n×m differentand/or same ones of the requests Q₁₁ . . . Q_(nm) (29) of the sameand/or different ones of the servers S₁ . . . S_(z) (20) present on thenetwork 24 at any time.

The queries QQ_(n1) . . . QQ_(nm) (53) may each be different, one fromthe other, or the same. The queries QS_(n1) . . . QS_(nu) (288)accessible to the user U_(n) (12) may each be different, one from theother, or the same. The hidden queries QH_(n1) . . . QH_(nh) (290) mayeach be different, one from the other, or the same. The number of thequeries QQ_(n1) . . . QQ_(nm) (53) “m” may be substantially the sum ofthe queries QS_(n1) . . . QS_(nu) (288) accessible to the user U_(n)(12) and the hidden queries QH_(n1) . . . QH_(nh) (290), i.e., m=u+h.

There may be m different or same ones of the queries QQ_(n1) . . .QQ_(nm) (53) corresponding to the requests Q_(n1) . . . Q_(nm) (29) fromthe client C_(n) (16) at any time, and n×m different and/or same ones ofthe queries QQ₁₁ . . . QQ_(nm) (53) corresponding to the requests Q₁₁ .. . Q_(nm) (29) of the same and/or different ones of the servers S₁ . .. S_(z) (20) present on the network 24 at any time.

The server addresses AQ_(n1) . . . AQ_(nm) (54) may each be different,one from the other, or the same. The server addresses A_(n1) . . .A_(nu) (265) accessible to the user U_(n) (12) may each be different,one from the other, or the same. The hidden server addresses AH_(n1) . .. AH_(nh) (291) may each be different, one from the other, or the same.The number of the server addresses AQ_(n1) . . . AQ_(nm) (54) “m” may besubstantially the sum of the server addresses A_(n1) . . . A_(nu) (265)accessible to the user U_(n) (12) and the hidden server addressesAH_(n1) . . . AH_(nh) (291), i.e., m=u+h.

There may be m different or same ones of the server addresses AQ_(n1) .. . AQ_(nm) (54) corresponding to the requests Q_(n1) . . . Q_(nm) (29)from the client C_(n) (16) at any time, and n×m different and/or sameones of the server addresses AQ₁₁ . . . AQ_(nm) (54) corresponding tothe requests Q₁₁ . . . Q_(nm) (29) of the same and/or different ones ofthe servers S₁ . . . S_(z) (20) present on the network 24 at any time.

The optional instructions VJ_(n1) . . . VJ_(nk) (52) may each bedifferent, one from the other, or the same. The optional instructionsV_(n1) . . . V_(nv) (289) accessible to the user U_(n) (12) may each bedifferent, one from the other, or the same. The optional hiddeninstructions H_(n1) . . . H_(ni) (292) may each be different, one fromthe other, or the same. The number of the optional instructions VJ_(n1). . . VJ_(nk) (52) “k” may be substantially the sum of the optionalinstructions V_(n1) . . . V_(nv) (289) accessible to the user U_(n) (12)and The optional hidden instructions H_(n1) . . . H_(ni) (292), i.e.,k=v+i.

There may be m×k different or same ones of the optional instructionsVJ_(n1) . . . VJ_(nk) (52) corresponding to the requests Q_(n1) . . .Q_(nm) (29) from the client C_(n) (16) at any time, and n×m×k differentand/or same ones of the optional instructions VJ₁₁ . . . VJ_(nk) (52)corresponding to the requests Q₁₁ . . . Q_(nm) (29) of the same and/ordifferent ones of the servers S₁ . . . S_(z) (20) present on the network24 at any time.

The requests Q₁₁ . . . Q_(nm) (29) of the servers S₁ . . . S_(z) (20)may be made at the same and/or different times. One or more of therequests Q₁₁ . . . Q_(nm) (29) may be made of each of the servers S₁ . .. S_(z) (20) by the same/and or different ones of the clients C₁ . . .C_(n) (16) and/or the server PS (18) at the same and/or different times.

The server PS (18) and/or the client C_(n) (16) may make one or more ofthe requests Q_(n1) . . . Q_(nm) (29) of the same and/or different onesof the servers S₁ . . . S_(z) (20), in accordance with the designationscheme corresponding to the corresponding ones of the serverdesignations S_(n1) . . . S_(nm) (30), in order to fulfill the servicesand/or information requirements of the user U_(n) (12).

K. Replies from the Servers

Each of the servers S₁ . . . S_(z) (20) communicated therewith repliesto the server PS (18) and/or the clients C₁ . . . C_(n) (16), inaccordance with the designation scheme which designates the servers S₁ .. . S_(z) (20) being communicated with corresponding to the requests Q₁₁. . . Q_(nm) (29) as the corresponding server designations S₁₁ . . .S_(nm) (30), and communicates the corresponding responses R₁₁ . . .R_(nm) (32), associated with the requests Q₁₁ . . . Q_(nm) (29), to theserver PS (18) and/or the clients C₁ . . . C_(n) (16) making therequests Q₁₁ . . . Q_(nm) (29).

Now, ones of the servers S₁ . . . S_(z) (20) having been contacted bythe server PS (18) and/or the clients C₁ . . . C_(n) (16) and theconnections OC₁₁ . . . OC_(nm) (323) opened therewith, corresponding tothe requests Q₁₁ . . . Q_(nm) (29), according to the server designationsS₁₁ . . . S_(nm) (30) at the corresponding server addresses A₁₁ . . .A_(nu) (265) at the corresponding ports W₁₁ . . . W_(nm) (343) reply tothe server PS (18) and/or the contacting clients C₁ . . . C_(n) (16)with the corresponding responses R₁₁ . . . R_(nm) (32).

A particular one of the responses R_(n1) . . . R_(nm) (32), hereinafterdesignated as the response R_(nm) (32), corresponding to one responsewithin the responses R_(n1) . . . R_(nm) (32), the response R_(nm) (32)corresponding to the request Q_(nm) (29), and the responses R_(n1) . . .R_(nm) (32) corresponding to the requests Q_(n1) . . . Q_(nm) (29), isshown schematically in FIG. 104.

Now, the response R_(nm) (32) may have a corresponding response headerline LR_(nm) (351), corresponding optional response header fieldsJR_(n1) . . . JR_(nt) (352), and a corresponding optional entity bodyRH_(nm) (353). The optional entity body RH_(nm) (353) typically haslinks, and/or descriptions, and/or other information. The request headerline LR_(nm) (351) may have a corresponding protocol BR_(nm) (354), acorresponding status SR_(nm) (355), and a corresponding statusexplanation SE_(nm) (356).

Ones of the connections may be closed after ones of the responses R₁₁ .. . R_(nm) (32) are communicated to the PS (18) and/or to the requestingcorresponding ones of the clients C₁ . . . C_(n) (16).

Again, the Timeout per Search Engine 329 is considered to besubstantially the maximum time for the server PS (18) and/or theparticular client C_(n) (16) making the requests Q_(n1) . . . Q_(nm)(29) to wait for each of the responses R_(n1) . . . R_(nm) (32) fromcertain ones of the servers S₁ . . . S_(z) (20), in accordance with thedesignation scheme which designates the certain ones of the servers S₁ .. . S_(z) (20) to be communicated with corresponding to the requests Q₁₁. . . Q_(nm) (29) as the corresponding server designations S₁₁ . . .S_(nm) (30).

If certain ones of the servers S₁ . . . S_(z) (20) do not openconnections OC₁₁ . . . OC_(nm) (323) with and/or communicate theresponses R₁₁ . . . R_(nm) (32) to the server PS (18) and/or the clientsC₁ . . . C_(n) (16), and/or if certain other ones of the servers S₁ . .. S_(z) (20) do not communicate the responses R₁₁ . . . R_(nm) (32) tothe server PS (18) and/or the clients C₁ . . . C_(n) (16) onceconnections OC₁₁ . . . OC_(nm) (323) therewith may have been opened,corresponding to the requests Q₁₁ . . . Q_(nm) (29), according to theserver designations S₁₁ . . . S_(nm) (30), within the timeout set by theTimeout per Search Engine 329, the certain ones of requests Q_(n1) . . .Q_(nm) (29) of such nonresponding ones of the servers S₁ . . . S_(z)(20) may then be cancelled by the server PS (18) and/or the clients C₁ .. . C_(n) (16). Information about such ones of the nonresponding ones ofthe servers S₁ . . . S_(z) (20) may then be communicated from the serverPS (18) and/or the clients C₁ . . . C_(n) (16) through the correspondingones of the user interfaces I₁ . . . I_(n) (14) to the correspondingones of the users U₁ . . . U_(n) (12), according to the serverdesignations S₁₁ . . . S_(nm) (30) corresponding to the certain ones ofrequests Q_(n1) . . . Q_(nm) (29) of such nonresponding ones of theservers S₁ . . . S_(z) (20).

In certain instances, the server PS (18) and/or certain ones of theclients C₁ . . . C_(n) (16) may contact certain ones of the servers S₁ .. . S_(z) (20) and open the connections OC₁₁ . . . OC_(nm) (323)therewith, corresponding to the requests Q₁₁ . . . Q_(nm) (29),according to the server designations S₁₁ . . . S_(nm) (30), one or moreadditional times, in order to satisfy the needs of the users U₁ . . .U_(n) (12), and/or certain requirements within the optional instructionsVJ_(n1) . . . VJ_(nk) (52), such as, for example, the URL's per SearchEngine 330, and/or as a result of certain information communicated tothe PS (18) and/or certain ones of the clients C₁ . . . C_(n) (16)within the responses R₁₁ . . . R_(nm) (32).

If, for example, less links, and/or descriptions, and/or prices/values,and/or images are returned within certain ones of the responses R₁₁ . .. R_(nm) (32), which may be considered to be first ones of the responsesR₁₁ . . . R_(nm) (32), than are requested by certain ones of the usersU₁ . . . U_(n) (12) within certain ones of the URL's per Search Engine330, the server PS (18) and/or certain ones of the clients C₁ . . .C_(n) (16) may contact certain ones of the servers S₁ . . . S_(z) (20),open the connections OC₁₁ . . . OC_(nm) (323) therewith, and makeadditional ones of the requests Q₁₁ . . . Q_(nm) (29), according to theserver designations S₁₁ . . . S_(nm) (30), one or more additional times,in order to satisfy the needs of the users U₁ . . . U_(n) (12). Thelinks, and/or the descriptions, and/or the images returned within and/orparsed from additional ones of the responses R₁₁ . . . R_(nm) (32) tothe additional ones of the requests Q₁₁ . . . Q_(nm) (29) may then beappended to the corresponding ones of the links, and/or thecorresponding ones of the descriptions, and/or the corresponding ones ofthe images returned within and parsed from the first ones of theresponses R₁₁ . . . R_(nm) (32)

The servers S₁ . . . S_(z) (20) communicate the responses R₁₁ . . .R_(nm) (32) to the requests Q₁₁ . . . Q_(nm) (29) to the server PS (18)and/or specific ones of the clients C₁ . . . C_(n) (16), in accordancewith the designation scheme corresponding to the corresponding ones ofthe server designations S₁₁ . . . S_(nm) (30). Alternatively, and/oradditionally, in certain instances, certain ones of the servers S₁ . . .S_(z) (20), corresponding to certain ones of the server designations S₁₁. . . S_(nm) (30), may request additional information of the server PS(18) and/or specific ones of the clients C₁ . . . C_(n) (16), prior tocommunicating the responses R₁₁ . . . R_(nm) (32) to the requests Q₁₁ .. . Q_(nm) (29). Upon receiving such additional information from theserver PS (18) and/or the specific ones of the clients C₁ . . . C_(n)(16), the certain ones of the servers S₁ . . . S_(z) (20), correspondingto the certain ones of the server designations S₁₁ . . . S_(nm) (30),may then communicate the responses R₁₁ . . . R_(nm) (32) to the requestsQ₁₁ . . . Q_(nm) (29) to the server PS (18) and/or the specific ones ofthe clients C₁ . . . C_(n) (16).

In such certain instances, in more detail, the server PS (18) and/orcertain ones of the clients C₁ . . . C_(n) (16) may contact certain onesof the servers S₁ . . . S_(z) (20) and open the connections OC₁₁ . . .OC_(nm) (323) therewith, corresponding to the requests Q₁₁ . . . Q_(nm)(29), according to the server designations S₁₁ . . . S_(nm) (30), one ormore additional times, as a result of certain information communicatedto the PS (18) and/or certain ones of the clients C₁ . . . C_(n) (16)within the responses R₁₁ . . . R_(nm) (32), such as, for example,information obtained from and/or parsed from the responses R₁₁ . . .R_(nm) (32). This information is typically within certain ones of theresponse header fields JR₁₁ . . . JR_(nt) (352), but may also be withinthe corresponding optional entity bodies RH₁₁ . . . RH_(nm) (353) and/orthe corresponding response header lines LR₁₁ . . . LR_(nm) (351).

Now, in such certain instances, the certain ones of the servers S₁ . . .S_(z) (20) request the information from the server PS (18) and/orcertain ones of the clients C₁ . . . C_(n) (16), prior to communicatingthe responses R₁₁ . . . R_(nm) (32) to the server PS (18) and/or thecertain ones of the clients C₁ . . . C_(n) (16). The server PS (18)and/or the certain ones of the clients C₁ . . . C_(n) (16) beingrequested such information may then respond to the requests for suchinformation, by communicating the requested information to the ones ofthe requesting servers S₁ . . . S_(z) (20). Upon receipt of therequested information at the ones of the requesting servers S₁ . . .S_(z) (20), the requesting ones of the servers S₁ . . . S_(z) (20) replyto the server PS (18) and/or the certain ones of the clients C₁ . . .C_(n) (16) with the responses R₁₁ . . . R_(nm) (32). Such requests forinformation from the servers S₁ . . . S_(z) (20) may occur not at all,and/or one or more times.

L. Parsing, Processing, Formatting, Sorting, Grouping, and OrganizingResponses into Service and/or Information Responses

A particular one of the optional entity bodies RH₁₁ . . . RH_(nm) (353),designated as the entity body RH_(nm) (353), of a particular one of theresponses R₁₁ . . . R_(nm) (32), designated as the response R_(nm) (32),may have optional response individual information groups LS_(nm1) . . .LS_(nmr) (360) and optional information LI_(nm) (361), as shown in FIG.105.

Each of the optional response individual information groups LS_(nm1) . .. LS_(nmr) (360) may have and/or be parsed into corresponding optionalresponse links LK_(nm1) . . . LK_(nmr) (362), and/or correspondingoptional response descriptions DK_(nm1) . . . DK_(nmr) (363), and/orcorresponding optional response prices/values PK_(nm1) . . . PK_(nmr)(364), and/or corresponding optional response images IK_(nm1) . . .IK_(nmr) (365), as shown in FIG. 105.

The optional response links LK_(nm1) . . . LK_(nmr) (362), thecorresponding optional response descriptions DK_(nm1) . . . DK_(nmr)(363), the corresponding optional response prices/values PK_(nm1) . . .PK_(nmr) (364), and the corresponding optional response images IK_(nm1). . . IK_(nmr) (365), corresponding to the optional response individualinformation groups LS_(nm1) . . . LS_(nmr) (360) are typicallyassociated correspondingly one with the other.

The optional response link LK_(nm1) (362), the corresponding optionalresponse description DK_(nm1) (363), the corresponding optional responseprice/value PK_(nm1) (364), and the corresponding optional responseimage IK_(nm1) (365), corresponding to the optional response individualinformation group LS_(nm1) (360) are typically associatedcorrespondingly one with the other. The optional response link LK_(nm2)(362), the corresponding optional response description DK_(nm2) (363),the corresponding optional response price/value PK_(nm2) (364), and thecorresponding optional response image IK_(nm2) (365), corresponding tothe optional response individual information group LS_(nm2) (360) aretypically associated correspondingly one with the other, and so on. Theoptional response link LK_(nmr) (362), the corresponding optionalresponse description DK_(nmr) (363), the corresponding optional responseprice/value PK_(nmr) (364), and the corresponding optional responseimage IK_(nmr) (365), corresponding to the optional response individualinformation group LS_(nmr) (360) are, thus, typically associatedcorrespondingly one with the other.

The optional information LI_(nm) (361) may have additional links, and/oradditional descriptions, and/or additional images, and/or prices/values,and/or other information, and/or services, and/or media, all and/or aportion of which may be used and/or discarded by the server PS (18)and/or the clients C₁ . . . C_(n) (16). The optional information LI_(nm)(361) is typically filtered from the optional entity body RH_(nm) (353)and discarded, and/or other unwanted information and/or media is alsotypically filtered from the response R_(nm) (32), and/or the optionalentity body RH_(nm) (353), and discarded.

The optional response individual information groups LS_(nm1) . . .LS_(nmr) (360) are typically parsed and/or processed and/or formattedfrom the entity body RH_(nm) (353) of the response R_(nm) (32), and/orparsed, and/or processed, and/or formatted, and/or organized, and/orgrouped into the addressable individual information groups LG_(nm1) . .. LG_(nmr) (80) of the addressable response information group RG_(nm)(57), correspondingly associated with the response R_(nm) (32), as shownin FIGS. 106 and 107.

FIG. 106 shows the addressable response information group RG_(nm) (57)having the addressable individual information groups LG_(nm1) . . .LG_(nmr) (80) parsed, and/or processed, and/or formatted, and/ororganized, and/or grouped into the addressable response informationgroup RG_(nm) (57) from the optional entity body RH_(nm) (353) of FIG.105.

FIG. 107 shows a particular one of the optional response individualinformation groups LS_(nm1) . . . LS_(nmr) (360), designated as theoptional response individual information group LS_(nmr) (360), parsed,and/or processed, and/or formatted, and/or organized, and/or groupedinto a particular one of the addressable individual information groupsLG_(nm1) . . . LG_(nmr) (80), designated as the addressable individualinformation group LG_(nmr) (80).

The addressable individual information groups LG_(nm1) . . . LG_(nmr)(80) are typically parsed, and/or processed, and/or formatted forconsistency of presentation and/or appearance one with the other, as theaddressable individual information groups LG_(nm1) . . . LG_(nmr) (80)are incorporated into the addressable response information groupsRG_(n1) . . . RG_(nm) (57) from the responses R_(n1) . . . R_(nm) (32).

Alternatively and/or additionally the addressable individual informationgroups LG_(nm1) . . . LG_(nmr) (80) may be incorporated into theaddressable response information groups RG_(n1) . . . RG_(nm) (57) fromthe responses R_(n1) . . . R_(nm) (32) in an as-is condition and/or inraw form.

The optional response links LK_(nm1) . . . LK_(nmr) (362) are typicallyparsed, and/or processed, and/or formatted into the correspondingoptional links LD_(nm1) . . . LD_(nmr) (82). The optional responsedescriptions DK_(nm1) . . . DK_(nmr) (363) are typically parsed, and/orprocessed, and/or formatted into the optional descriptions DD_(nm1) . .. DD_(nmr) (83). The optional response prices/values PK_(nm1) . . .PK_(nmr) (364) are typically parsed, and/or processed, and/or formattedinto the corresponding optional prices/values PD_(nm1) . . . PD_(nmr)(84). The optional response images IK_(nm1) . . . IK_(nmr) (365) aretypically parsed, and/or processed, and/or formatted into thecorresponding optional images ID_(nm1) . . . ID_(nmr) (85).

Each of the optional links LD_(m1) . . . LD_(mr) (82) are also typicallyparsed, and/or processed, and/or formatted for consistency ofpresentation and/or appearance one with the other. Alternatively and/oradditionally the optional links LD_(nm1) . . . LD_(nmr) (82) may beretained in an as-is condition and/or in raw form.

Each of the optional descriptions DD_(nm1) . . . DD_(nmr) (83) are alsotypically parsed, and/or processed, and/or formatted for consistency ofpresentation and/or appearance one with the other. Alternatively and/oradditionally the optional links optional descriptions DD_(nm1) . . .DD_(nmr) (83) may be retained in an as-is condition and/or in raw form.

Each of the optional prices/values PD_(nm1) . . . PD_(nmr) (84) are alsotypically parsed, and/or processed, and/or formatted for consistency ofpresentation and/or appearance one with the other. Alternatively and/oradditionally the optional prices/values PD_(nm1) . . . PD_(nmr) (84) maybe retained in an as-is condition and/or in raw form.

Each of the optional images ID_(nm1) . . . ID_(nmr) (85) are alsotypically parsed, and/or processed, and/or formatted for consistency ofpresentation and/or appearance one with the other. Alternatively and/oradditionally the optional images ID_(nm1) . . . ID_(nmr) (85) may beretained in an as-is condition and/or in raw form.

The optional links LD_(nm1) . . . LD_(nmr) (82), and/or the optionaldescriptions DD_(nm1) . . . DD_(nmr) (83), and/or the optionalprices/values PD_(nm1) . . . PD_(nmr) (84), and/or the optional imagesID_(nm1) . . . ID_(nmr) (85), correspondingly associated with theresponse R_(nm) (32), may additionally and/or alternatively be parsedindividually and/or separately, and incorporated into the addressableresponse information group RG_(nm) (57) from the optional entity bodyRH_(nm) (353), as shown in FIG. 108.

The response header line LR_(nm) (351) and/or the optional responseheader fields JR_(n1) . . . JR_(nt) (352) may also have information,which the server PS (18) and/or the clients C₁ . . . C_(n) (16) may use.

The optional information LI_(nm) (361) and/or certain information and/ormedia within the response R_(nm) (32), particularly within the optionalentity body RH_(nm) (353), may be optionally used by the server PS (18)and/or the clients C₁ . . . C_(n) (16), and/or optionally incorporatedinto the addressable response information group RG_(nm) (57).

Each of the optional response individual information groups LS_(nm1) . .. LS_(nmr) (360) from each of the responses R_(n1) . . . R_(nm) (32) maybe compared one with the other, and duplicate ones of the of theoptional response individual information groups LS_(nm1) . . . LS_(nmr)(360) may be discarded.

Alternatively and/or additionally, each of the optional addressableindividual information groups LG_(n11) . . . LG_(nmr) (80) from each ofthe addressable response information groups RG_(n1) . . . RG_(nm) (57)may be compared one with the other, and duplicate ones of the optionaladdressable individual information groups LG_(n11) . . . LG_(nmr) (80)may be discarded.

Each of the optional response individual information groups LS₁₁₁ . . .LS_(nmr) (360) and/or portions thereof from the entity bodies RH₁₁ . . .RH_(nm) (353) of the responses R₁₁ . . . R_(nm) (32) may also beoptionally compared one with the other, and duplicate ones of the of theoptional response individual information groups LS₁₁₁ . . . LS_(nmr)(360) may be optionally discarded.

Alternatively and/or additionally, each of the optional links LK_(n11) .. . LK_(nmr) (362), and/or the optional descriptions DK_(n11) . . .DK_(nmr) (363), and/or the optional prices/values PK_(nm1) . . .PK_(nmr) (364), and/or the optional images IK_(n11) . . . IK_(nmr)(365), from each of the responses R_(n1) . . . R_(nm) (32) may becompared one with the other of like kind, and duplicate ones of theoptional links LK_(n11) . . . LK_(nmr) (362), and/or the optionaldescriptions DK_(n11) . . . DK_(nmr) (363), and/or the optionalprices/values PK_(nm1) . . . PK_(nmr) (364), and/or the optional imagesIK_(n11) . . . IK_(nmr) (365), and/or a combination thereof may bediscarded.

Alternatively and/or additionally, each of the optional links LD_(n11) .. . LD_(nmr) (82), and/or the optional descriptions DD_(n11) . . .DD_(nmr) (83), and/or the optional prices/values PD_(nm1) . . . PD_(nmr)(84), and/or the optional images ID_(n11) . . . ID_(nmr) (85) from eachof the addressable response information groups RG_(n1) . . . RG_(nm)(57) may be compared one with the other of like kind, and duplicate onesof the optional links LD_(n11) . . . LD_(nmr) (82), and/or the optionaldescriptions DD_(n11) . . . DD_(nmr) (83), and/or the optionalprices/values PD_(nm1) . . . PD_(nmr) (84), and/or the optional imagesID_(n11) . . . ID_(nmr) (85), and/or a combination thereof may bediscarded.

The optional links LK_(n11) . . . LK_(nmr) (362) are typically comparedone with the other, and duplicate ones of the corresponding optionallinks LK_(n11) . . . LK_(nmr) (362), and/or the corresponding optionaldescriptions DK_(n11) . . . DK_(nmr) (363), and/or the correspondingoptional images IK_(n11) . . . IK_(nmr) (365), and/or the correspondingoptional prices/values PK_(nm1) . . . PK_(nmr) (364) are discarded,leaving only one of any ones of the duplicate optional links LK_(n11) .. . LK_(nmr) (362) and/or the corresponding optional descriptionsDK_(n11) . . . DK_(nmr) (363), and/or the corresponding optional imagesIK_(n11) . . . IK_(nmr) (365), and/or the optional prices/valuesPK_(nm1) . . . PK_(nmr) (364) remaining.

The optional prices/values PD_(nm1) . . . PD_(nmr) (84) and/or thecorresponding optional links LD_(n11) . . . LD_(nmr) (82) and/or thecorresponding optional descriptions DD_(n11) . . . DD_(nmr) (83), and/orthe corresponding optional images ID_(n11) . . . ID_(nmr) (85) may besorted with respect to the optional prices/values PD_(nm1) . . .PD_(nmr) (84), in accordance with sorting criteria in the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) and/or in accordance withdefault criteria resident within the server PS (18) and/or the clientC_(n) (16).

The optional links LD_(n11) . . . LD_(nmr) (82), and/or thecorresponding optional descriptions DD_(n11) . . . DD_(nmr) (83), and/orthe corresponding optional prices/values PD_(nm1) . . . PD_(nmr) (84),and/or the corresponding optional images ID_(n11) . . . ID_(nmr) (85)may be sorted, for example, in ascending order with respect to theoptional prices/values PD_(nm1) . . . PD_(nmr) (84) having the lowestprice therein being presented to the user U_(n) (12) at the userinterface I_(n) (14) first and the highest price therein last.

Alternatively and/or additionally, the optional links LD_(n11) . . .LD_(nmr) (82), and/or the corresponding optional descriptions DD_(n11) .. . DD_(nmr) (83), and/or the corresponding optional prices/valuesPD_(nm1) . . . PD_(nmr) (84), and/or the corresponding optional imagesID_(n11) . . . ID_(nmr) (85) may be sorted, for example, in ascending ordescending alphabetical order with respect to the optional linksLD_(n11) . . . LD_(nmr) (82) and/or the corresponding optionaldescriptions DD_(n11) . . . DD_(nmr) (83) being presented to the userU_(n) (12) at the user interface I_(n) (14).

Other sorting criteria may be used for the optional links LD_(n11) . . .LD_(nmr) (82), and/or the optional descriptions DD_(n11) . . . DD_(nmr)(83), and/or the optional prices/values PD_(nm1) . . . PD_(nmr) (84),and/or the optional images ID_(n11) . . . ID_(nmr) (85), and may dependupon needs of the user U_(n) (12). The sorting criteria may bedetermined by the user U_(n) (12).

Sorting criteria gives the user U_(n) (12) the ability to formulate howinformation is presented to the user U_(n) (12) at the user interfaceI_(n) (14), and may be incorporated into the optional instructionsVJ_(n1) . . . VJ_(nk) (52), which may be entered into the user interfaceI_(n) (14) through the user input UI_(n) (25) by the user U_(n) (12).The sorting criteria may additionally and/or alternatively be residentwithin the server PS (18) and/or the client C_(n) (16).

Now again, the labelled individual information group LL_(nzu) (86)associated with the addressable query information group GI_(nz) (63) hasthe optional group identifier GL_(nc) (87), the optional query linkidentifier LN_(ncu) (88), the optional resource location identifierSU_(nw) (89), the optional server and/or query identifier SI_(nm) (90),and/or the optional server link identifier LX_(nmr) (91) appended to theaddressable individual information group LG_(nmr) (80), as shown in FIG.68.

FIGS. 109 and 110 show typical ones of the addressable query informationgroup GI_(nz) (63), based upon certain sorting and/or grouping criteria,having the labelled individual information groups LL_(n11) . . .LL_(nzu) (86), the optional database labelled individual informationgroups RL_(nz1) . . . RL_(nzx) (92), the optional query descriptionQT_(nz) (93), the optional server descriptions and/or links ST_(nz1) . .. ST_(nzf) (94), and the optional advertisements and/or links ST_(nz1) .. . ST_(nzf) (95) incorporated into certain typical ones of the typicalservice and/or information response forms IS_(n) (39) of FIGS. 27A-52C,inclusive.

The client-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and the multitasking process 104,the server PS (18) and/or the clients C₁ . . . C_(n) (16), then, arecapable of retrieving, parsing, processing, formatting, organizing,grouping, sorting, and consolidating services and/or information fromthe same and/or different ones of the servers S₁ . . . S_(z) (20),and/or the optional servers SO₁ . . . SO_(p) (22), and/or the clients C₁. . . C_(n) (16), having the same and/or different structures, formats,organizations, groupings, and/or data structures, and incorporating theparsed, processed, formatted, organized, grouped, sorted, andconsolidated services and/or information into the user responses UR₁ . .. UR_(n) (37) for delivery to the user interfaces I₁ . . . I_(n) (14)and use by the users U₁ . . . U_(n) (12).

The client-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and the multitasking process 104,the server PS (18) and/or the clients C₁ . . . C_(n) (16), then, arecapable of retrieving, parsing, processing, formatting, organizing,grouping, sorting, and consolidating services and/or information fromthe same and/or different ones of each of the optional responseindividual information groups LS₁₁₁ . . . LS_(nmr) (360), and/or theoptional response links LK₁₁₁ . . . LK_(nmr) (362), and/or the optionalresponse descriptions DK₁₁₁ . . . DK_(nmr) (363), and/or the optionalresponse prices/values PK₁₁₁ . . . PK_(nmr) (364), and/or the optionalresponse images IK_(nm1) . . . IK_(nmr) (365) from the entity bodiesRH₁₁ . . . RH_(nm) (353) of the responses R₁₁ . . . R_(nm) (32), havingthe same and/or different structures, formats, organizations, groupings,and/or data structures, and incorporating the parsed, processed,formatted, organized, grouped, sorted, and consolidated services and/orinformation into the user responses UR₁ . . . UR_(n) (37) for deliveryto the user interfaces I₁ . . . I_(n) (14) and use by the users U₁ . . .U_(n) (12).

M. Additional Features and/or Other Considerations

The present invention is directed to a client-server multitasking systemand process capable of information and/or service retrieval from thesame and/or different ones of servers substantially simultaneously andon-the-fly, using the same and/or different ones of queries of the sameand/or different ones of the servers, and sorting, grouping, and/ororganizing responses therefrom substantially on-the-fly, andcommunicating service and/or information responses to the requestersand/or users substantially simultaneously and on-the-fly. Theclient-server multitasking system and process are capable of use on avariety of networks, such as global area networks, and in particular,the internet, metropolitan area networks, wide area networks, and localarea networks, and be capable of searching search engines and/or othersites substantially simultaneously and on-the-fly.

The client-server multitasking system and process are capable ofretrieving substantially multiple simultaneous services and/orinformation having the same and/or different criteria from the sameand/or different servers, sorting, grouping, and/or organizing theresponses from the servers and/or the clients into information and/orservices responses, and communicating the service and/or informationresponses to the requesters and/or users substantially simultaneously.The requesters and/or the users may make substantially simultaneousservice and/or information requests of servers and clients, using thesame and/or different queries, and/or the same and/or differentinstructions. The same and/or different uniform resource locators,target resources, and/or paths may be used.

The client-server multitasking system and process are capable of makingmultiple substantially simultaneous same and/or different requests ofthe same and/or different servers, organizing responses from the serversinto service and/or information responses, and communicating the serviceand/or information responses to the requesters and/or the userssubstantially simultaneously.

The client-server multitasking system and process are also capable ofsorting, grouping, and/or organizing results from the servers, searchengines, and/or sites, in accordance with instructions from therequesters, and/or the users, and/or instructions resident within theclient-server multitasking system and/or process. The client-servermultitasking system is capable of use in a variety of applications, andis capable of information comparison and/or trend analysis ofinformation from the same and/or different sources substantiallysimultaneously. The client-server multitasking system and process arealso capable of building a client-server multitasking system searchengine and/or database from responses returned from the servers, searchengines, and/or sites being queried and/or searched, and/or havingrequests made thereof, are capable of being searched and/or queried,querying sites referenced in the client-server multitasking systemsearch engine and/or database, and updating information and/or servicesstored therein.

The client-server multitasking system and process are capable ofinformation and/or service retrieval from the same and/or different onesof servers substantially simultaneously and on-the-fly, using the sameand/or different ones of queries, and sorting, grouping, and/ororganizing responses therefrom substantially on-the-fly.

A requester and/or user is capable of making substantially multiplesimultaneous same and/or different requests of the same and/or differentservers. The client server-multitasking system and process are capableof organizing responses from the servers into service and/or informationresponses, and communicating the service and/or information responses tothe requesters and/or the users substantially simultaneously, andon-the-fly.

The requesters and/or users are capable of making substantiallysimultaneous service and/or information requests of the same and/ordifferent ones of servers and/or clients, using the same and/ordifferent queries, and/or the same and/or different instructions. Theclient-server multitasking system and process are capable of retrievingsubstantially multiple simultaneous services and/or information havingthe same and/or different criteria from the same and/or differentservers, sorting, grouping, and/or organizing the responses from theservers and/or the clients into information and/or services responses,and communicating the service and/or information responses to therequesters and/or the users substantially simultaneously. The sameand/or different ones of uniform resource locators, target resources,and/or paths may be used.

The requesters and/or users are capable of making multiple simultaneoussearches. The searches may have at least one or a plurality of same ordifferent queries of the same and/or different servers and/or clients.The responses from the servers and/or the clients may be of beingorganized into the service and/or information response in a variety offormats. The responses may be sorted within the service and/orinformation response, such as, for example, by category, query, group,page, order of importance, ascending and/or descending order,alphabetically and/or numerically, or other characteristics, asdetermined by the requester, and/or the user, and/or the client-servermultitasking system, and/or the responses may be combined within theservice and/or information response, such as, for example, interleavingthe responses one with the other, such as, for example, by order ofrelevance or other parameters. The responses may also be capable ofbeing grouped by search criteria, server, order of importance, or bynumerical factors such as value, price, or other numerical quantifier.The responses may be presentable, for example, in ascending ordescending order in interleaved format, such as top ones, twos, threes,and so on, or presentable separately to the requestor and/or the user.The order may be order of importance or relevance related, or, forexample, numerically valued, such as price or stock market value.

The client-server multitasking system and process are capable ofinformation and/or service retrieval from the same and/or different onesof the servers substantially simultaneously and on-the-fly, using thesame and/or different ones of the queries, and sorting, grouping, and/ororganizing responses therefrom substantially on-the-fly.

The client-server multitasking system and process are capable ofsubstantially multiple simultaneous searching, using the same and/ordifferent ones of queries of the same and/or different ones of theclients and/or servers, which may be search engines, and/or sites,and/or servers, and/or locations on the network, and additionally and/oralternatively building a client-server multitasking search engine and/ordatabase. The client-server multitasking search engine and/or databaseare capable of storing the information and/or services retrieved fromthe search engines, and/or sites, and/or servers, and/or locations beingqueried on the network therein, and building the client-server searchengine and/or database. The client-server multitasking search engine isalso capable of being queried either directly and/or in combination withthe substantially simultaneous searching, using the same and/ordifferent queries of the same and/or different search engines, sites,servers, and/or databases. The client-server multitasking search engineand/or database are also capable of updating information and/or servicesstored therein by querying sites, servers, search engines, and/ordatabases containing information and/or services referenced in theclient-server multitasking search engine and/or database.

The client-server multitasking system and process are also capable ofuse on a variety of networks, such as global area networks, and inparticular, the internet, metropolitan area networks, wide areanetworks, and local area networks.

The client-server multitasking system and process are capable ofsubstantially simultaneous searching of the same and/or different onesof search engines and/or sites on the network substantially on-the-fly,with the same and/or different ones of the queries, and sorting,grouping, and/or organizing responses therefrom substantiallyon-the-fly.

The client-server multitasking system and process are also capable ofsorting, grouping, and/or organizing results from the servers, searchengines, and/or sites, in accordance with instructions from therequesters and/or the users, and/or instructions resident within theclient-server multitasking system and/or process. The client-servermultitasking system and process are also capable of drilling down and/orup to different levels within the search engines, sites, and/or serversbeing queried.

The client-server multitasking system and process are capable ofproviding manual and/or timed updates. Such timed updates allow formotion related presentation to the requestor and/or the user.

The client-server multitasking system and process are capable ofincorporating information and/or services into a variety of userinterfaces at different locations in the user interfaces, grouping,and/or organizing the information and/or services, and optionallyeliminating duplicate information and/or services.

The client-server multitasking system and process are capable ofincorporating links, graphics, video, text, and audio, and/orcombinations thereof, and selective advertising, according to selectablesearch, query, sorting, and/or grouping criteria, and/or combinationsthereof into the information and/or services to be delivered to the userinterfaces. The requester and/or the user may place orders, such aspurchases, and/or other types of orders, payments, confirmationsthereof, and/or combinations thereof, either directly and/or throughservers and/or sites on the network.

The client-server multitasking system is capable of use in a variety ofapplications, and is capable of information comparison and/or trendanalysis of information from the same and/or different sourcessubstantially simultaneously. The client-server multitasking system iscapable of, for example, determining best query results, with respect toa plurality of search engine results; purchasing and/or pricecomparisons, viewing and/or reviewing prices/values and trends fordifferent sites, determining lowest costs and lowest cost analyses forwholesale and retail purposes; product availability, e.g., airlinetickets, pricing, and ticket availability, from different airlines tothe same and/or different locations; purchasing of commodities and/orstocks form the same and/or different sites with updates every fewseconds and/or minutes; obtaining prices and/or values in differentstock markets substantially simultaneously; and searching for jobs onthe same and/or different job sites, using the same and/or different jobcriteria, for example, on a daily basis, the job sites having changingjob availability; and/or a combination thereof, all substantiallysimultaneously. The client-server multitasking system is capable ofpresenting information and/or services for review and/or updating fromthe same and/or different ones of sites, servers, and/or applicationssubstantially simultaneously, and trend analysis thereof, using avariety of sorting, grouping and/or organizing criteria, according tothe needs of the requestor, and/or the user, and/or resident within theclient-server multitasking system.

The client server-multitasking system and process are capable of serviceand/or information retrieval from at least one server, organization,communication, and presentation of such services and/or information toat least one requestor and/or user, and/or optional storage, and/orretrieval of such services and/or information from the optional storage.The client-server multitasking system and process are capable ofbuilding a client-server multitasking system search engine and/ordatabase from responses returned from the servers, search engines,and/or sites being queried and/or searched, and/or having requests madethereof The client-server multitasking system search engine and/ordatabase having stored information and/or services therein are alsosearchable, are capable of full text searches thereof, and aresearchable by the servers and/or the clients on the network, eitherseparately and/or in combination with the substantially simultaneousmultiple same and/or different searches and/or queries of the sameand/or different servers on the network. Information in theclient-server multitasking system search engine and/or database are alsosearchable and/or retrievable, and are capable of being incorporatedinto the service and/or information responses delivered to the userinterfaces, according to search criteria, selectively and/orautomatically, by the requestor and/or the user. The client-servermultitasking system search engine and/or database are capable ofspidering, and/or roboting, and/or querying sites, services and/orinformation to be stored therein and/or stored in the client-servermultitasking system search engine and/or database, and updating theservices and/or information to be stored and/or stored in theclient-server multitasking system search engine and/or database.

The client-server multitasking system and process, then, are capable ofinformation and/or service retrieval from the same and/or different onesof servers substantially simultaneously and on-the-fly, using the sameand/or different ones of queries of the same and/or different ones ofthe servers, and sorting, grouping, and/or organizing responsestherefrom substantially on-the-fly, and communicating service and/orinformation responses to the requestors and/or users substantiallysimultaneously and on-the-fly. The client-server multitasking system andprocess are capable of use on a variety of networks, such as global areanetworks, and in particular, the internet, metropolitan area networks,wide area networks, and local area networks, and are capable ofsearching search engines and/or other sites substantially simultaneouslyand on-the-fly. The client-server multitasking system and process arecapable of sorting, grouping, and/or organizing results from theservers, search engines, and/or sites, in accordance with instructionsfrom the requesters, and/or users, and/or instructions resident withinthe client-server multitasking system and/or process. The client-servermultitasking system is capable of use in a variety of applications, andis capable of information comparison and/or trend analysis ofinformation from the same and/or different sources substantiallysimultaneously. The client-server multitasking system and process arecapable of building a client-server multitasking system search engineand/or database from responses returned from the servers, searchengines, and/or sites being queried and/or searched, and/or havingrequests made thereof, is capable of being searched and/or queried,querying sites referenced in the client-server multitasking systemsearch engine and/or database, and updating information and/or servicesstored therein.

The client-server multitasking system and process are capable ofretrieving, parsing, processing, formatting, organizing, grouping,sorting, and consolidating services and/or information from the sameand/or different ones of the servers and/or clients having the sameand/or different structures, formats, organizations, groupings, and/ordata structures, and incorporating the parsed, processed, formatted,organized, grouped, sorted, and consolidated services and/or informationinto user responses for delivery to and use by the requestors and/orusers.

The client-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and the multitasking process 104,the server PS (18) and/or the clients C₁ . . . C_(n) (16), then, arecapable of retrieving, parsing, processing, formatting, organizing,grouping, sorting, and consolidating services and/or information fromthe same and/or different ones of the servers S₁ . . . S_(z) (20),and/or the optional servers SO₁ . . . SO_(p) (22), and/or the clients C₁. . . C_(n) (16), having the same and/or different structures, formats,organizations, groupings, and/or data structures, and incorporating theparsed, processed, formatted, organized, grouped, sorted, andconsolidated services and/or information into the user responses UR₁ . .. UR_(n) (37) for delivery to the user interfaces I₁ . . . I_(n) (14)and use by the users U₁ . . . U_(n) (12).

The client-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and the multitasking process 104,which in itself is a process, the user interfaces I₁ . . . I_(n) (14),and/or the clients C₁ . . . C_(n) (16), and/or the server PS (18),and/or the servers S₁ . . . S_(z) (20), and/or the optional servers SO₁. . . SO_(p) (22) may be constructed of hardware, firmware, software,machines, and/or operating systems, and/or combinations thereof, and/orother suitable means, and/or other components and/or systems, and/orcombinations thereof. Such hardware, firmware, software, machines,and/or operating systems, and/or combinations thereof, other componentsand/or systems, and/or other suitable means, and/or combinations thereofmay have therein and/or be resident therein, but are not limited tocomputer components and/or systems, television and/or telecommunicationscomponents and/or systems, merger of television and computer systems,and/or merger of television and/or computer and/or telecommunicationssystems, networks, simulators, interactive technologies and/or systems,cybernetics and/or cybernetic systems, and/or combinations thereof.

The clients C₁ . . . C_(n) (16), the server PS (18), the servers S₁ . .. S_(z) (20), and/or the optional servers SO₁ . . . SO_(p) (22) may besearch engines, and/or sites, and/or servers, and/or clients, and/orURL's, and/or databases, and/or locations on the network, and/or othersuitable components and/or systems, and/or other suitable means, and/orcombinations thereof, which may be capable of communicating on thenetwork 24. The scope of the client-server multitasking system 10 of thepresent invention, the client-server multitasking process 99, and themultitasking process 104, however, is not limited to search engines,and/or sites, and/or servers, and/or clients, and/or URL's, and/ordatabases, and/or locations on the network, and/or other suitablecomponents and/or systems, and/or other suitable means, and/orcombinations thereof, which may be capable of communicating on thenetwork 24, as it is recognized that other components, systems,technologies, and/or operating systems exist and/or emerge that may makeuse of the benefits of the present invention, and are either on thehorizon and/or are recognized to be forthcoming.

The client-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and the multitasking process 104,which in itself is a process, the user interfaces I₁ . . . I_(n) (14),and/or the clients C₁ . . . C_(n) (16), and/or the server PS (18),and/or the servers S₁ . . . S_(z) (20), and/or the optional servers SO₁. . . SO_(p) (22), may then be hardware, firmware, software, and/ormachines, and/or operating systems, and/or other suitable means, and/orcombinations thereof, and may have and/or be resident within generalpurpose computers, special purpose computers, televisions,computer-television combinations, telecommunications systems, networks,mergers of computer and/or television technology and/ortelecommunications technology and/or network technology, media, film,entertainment, interactive technologies and/or systems, cyberneticsand/or cybernetic systems and/or technology, components, and/or systems,and/or other suitable means, and/or combinations thereof, and may beintegrated one with the other and/or with other components and/orsystems of one another, and may each be substantially the same and/ordifferent one from the other.

The client-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and the multitasking process 104,which in itself is a process, the user interfaces I₁ . . . I_(n) (14),and/or the clients C₁ . . . C_(n) (16), and/or the server PS (18),and/or the servers S₁ . . . S_(z) (20), and/or the optional servers SO₁. . . SO_(p) (22) may each have the same and/or different hardware,firmware, software, and/or ones of operating systems, and/or othersuitable means, and/or combinations thereof. The optional databases 41and/or 42 may also be hardware, firmware, software, and/or machinebased, and/or other suitable means, and/or combinations thereof, havethe same and/or different ones of operating systems and/or combinationsthereof, and may have memory components associated therewith.

The client-server multitasking system and process are capable of use ona variety of networks, such as global area networks, and in particular,the internet, metropolitan area networks, wide area networks, and localarea networks. Such networks may be Earth based, satellite based, and/orspace based, and/or other suitable means, and/or combinations thereof.

The scope of the client-server multitasking system 10 of the presentinvention, the client-server multitasking process 99, and themultitasking process 104, however, is not limited to such components,systems, technologies, operating systems and/or networks, as othercomponents, systems, technologies, and/or operating systems exist and/oremerge that may make use of the benefits of the present invention, andare either on the horizon and/or are recognized to be forthcoming.

Determination as to whether the server PS (18) performs the multitaskingprocess 104, and/or whether particular ones of the clients C₁ . . .C_(n) (16) perform the multitasking process 104, may optionally be madeat the particular ones of the clients C₁ . . . C_(n) (16) and/or theserver PS (18). Such determination may optionally be made by the usersU₁ . . . U_(n) (12), and/or be based upon processing power,capabilities, and/or configurations of the particular ones of theclients C₁ . . . C_(n) (16), the server PS (18), and the network 24considerations (traffic, load, and/or other considerations).

The client-server multitasking search engine and/or database are capableof updating information and/or services stored therein by queryingsites, servers, search engines, and/or databases containing informationand/or services referenced in the client-server multitasking searchengine and/or database.

The client-server multitasking system and process are capable of use ona variety of networks, such as global area networks, and in particular,the internet, metropolitan area networks, wide area networks, and localarea networks, and is capable of searching search engines and/or othersites substantially simultaneously and on-the-fly.

The client-server multitasking system and process are capable ofsubstantially simultaneous searching of the same and/or different onesof search engines and/or sites on the network substantially on-the-fly,with the same and/or different ones of the queries, and sorting,grouping, and/or organizing responses therefrom substantiallyon-the-fly.

The client-server multitasking system and process are also capable ofsorting, grouping, and/or organizing results from the servers, searchengines, and/or sites, in accordance with instructions from therequesters, and/or instructions resident within the client-servermultitasking system and/or process. The client-server multitaskingsystem and process are also capable of drilling down and/or up todifferent levels within the search engines, sites, and/or servers beingqueried.

Now again, the typical ones of the service and/or information entryrequest forms IE₁ . . . IE_(n) (38) at the user interfaces I₁ . . .I_(n) (14) shown in FIGS. 5A, 5B, and 6-10 are typical examples of theservice and/or information entry request forms IE₁ . . . IE_(n) (38) atthe user interfaces I₁ . . . I_(n) (14), a much larger variety of whichis possible. Names and/or links and/or other information areincorporated in the typical ones of the service and/or information entryrequest forms IE₁ . . . IE_(n) (38) shown in FIGS. 5A, 5B, and 6-10 forillustrative purposes, and are not intended to limit the large varietyof the service and/or information entry request forms IE₁ . . . IE_(n)(38) and the names and/or links and/or information that are possible,and that may be incorporated into the service and/or information entryrequest forms IE₁ . . . IE_(n) (38) at the user interfaces I₁ . . .I_(n) (14).

Now again, The typical ones of the completed service and/or informationentry request forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . .. I_(n) (14) shown in FIGS. 11-26 are typical examples of the completedservice and/or information entry request forms IF₁ . . . IF_(n) (230) atthe user interfaces I₁ . . . I_(n) (14), a much larger variety of whichis possible. Typical queries QQ_(n1) . . . QQ_(nm) (53), typical serveraddresses AQ_(n1) . . . AQ_(nm) (54), and typical optional instructionsVJ_(n1) . . . VJ_(nk) (52) in the typical ones of the completed serviceand/or information entry request forms IF₁ . . . IF_(n) (230) at theuser interfaces I₁ . . . I_(n) (14) shown in FIGS. 11-26 are typicalexamples for illustrative purposes, and are not intended to limit thesubstantially infinite variety of the queries QQ_(n1) . . . QQ_(nm)(53), the server addresses AQ_(n1) . . . AQ_(nm) (54), and the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) that may be entered into theservice and/or information entry request forms IE₁ . . . IE_(n) (38), toderive the completed service and/or information entry request forms IF₁. . . IF_(n) (230) at the user interfaces I₁ . . . I_(n) (14). Likewise,names and/or links and/or other information are incorporated in thetypical ones of the completed service and/or information entry requestforms IF₁ . . . IF_(n) (230) shown in FIGS. 11-26 for illustrativepurposes, and are not intended to limit the large variety of thecompleted service and/or information entry request forms IF₁ . . .IF_(n) (230) and the names and/or links and/or information that arepossible, and that may be incorporated into the completed service and/orinformation entry request forms IF₁ . . . IF_(n) (230) at the userinterfaces I₁ . . . I_(n) (14).

Now again, the typical ones of the user responses UR₁ . . . UR_(n) (37),as typical service and/or information response forms IS₁ . . . IS_(n)(39) at the user interfaces I₁ . . . I_(n) (14) shown in FIG. 27A-52C,inclusive, are typical examples of the user responses UR₁ . . . UR_(n)(37), as typical service and/or information response forms IS₁ . . .IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14), a much largervariety of which is possible. FIGS. 27A-52C, inclusive, illustratetypical examples of typical ones of the user responses UR₁ . . . UR_(n)(37), as typical service and/or information response forms IS₁ . . .IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14) to the typicalqueries typical queries QQ_(n1) . . . QQ_(nm) (53), the typical ones ofthe server addresses AQ_(n1) . . . AQ_(nm) (54), and the typicaloptional instructions VJ_(n1) . . . VJ_(nk) (52) having been enteredinto the typical ones of the completed service and/or information entryrequest forms IF₁ . . . IF_(n) (230) at the user interfaces I₁ . . .I_(n) (14) shown in FIGS. 11-26.

The typical examples of the typical ones of the user responses UR₁ . . .UR_(n) (37), as typical service and/or information response forms IS₁ .. . IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14) are forillustrative purposes, and are not intended to limit the substantiallyinfinite variety of the user responses UR₁ . . . UR_(n) (37), as theservice and/or information response forms IS₁ . . . IS_(n) (39) at theuser interfaces I₁ . . . I_(n) (14), the queries QQ_(n1) . . . QQ_(nm)(53), the server addresses AQ_(n1) . . . AQ_(nm) (54), and the optionalinstructions VJ_(n1) . . . VJ_(nk) (52) that may be entered into theservice and/or information entry request forms IE₁ . . . IE_(n) (38), toderive the to the completed service and/or information entry requestforms IF₁ . . . IF_(n) (230), and which result in the user responses UR₁. . . UR_(n) (37), as the service and/or information response forms IS₁. . . IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14). Likewise,names and/or links and/or other information are incorporated into thetypical ones of the user responses UR₁ . . . UR_(n) (37), as the serviceand/or information response forms IS₁ . . . IS_(n) (39) at the userinterfaces I₁ . . . I_(n) (14), shown in FIGS. 27A-52C, inclusive, forillustrative purposes, and are not intended to limit the large varietyof the user responses UR₁ . . . UR_(n) (37), as the service and/orinformation response forms IS₁ . . . IS_(n) (39) at the user interfacesI₁ . . . I_(n) (14), and the names and/or links and/or information thatare possible, and that may be incorporated into the user responses UR₁ .. . UR_(n) (37), as the service and/or information response forms IS₁ .. . IS_(n) (39) at the user interfaces I₁ . . . I_(n) (14).

The server addresses AQ_(n1) . . . AQ_(nm) (54), such as WebCrawler®,Altavista®, Lycos®, Infoseek®, Excite®, Yahoo®, LookSmart®, HotBot®,Dejanews®, Amazon®, Borders®, BarnesandNoble®, Google®, and/or othersthat may have been used herein are for illustrative purposes, toillustrate typical ones of the service and/or information entry requestforms IE₁ . . . IE_(n) (38) at the user interfaces I₁ . . . I_(n) (14)shown in FIGS. 5A, 5B, and 6-10, typical ones of the completed serviceand/or information entry request forms IF₁ . . . IF_(n) (230) at theuser interfaces I₁ . . . I_(n) (14) shown in FIG. 11-26, and/or typicalones of the user responses UR₁ . . . UR_(n) (37), as the service and/orinformation response forms IS₁ . . . IS_(n) (39) at the user interfacesI₁ . . . I_(n) (14), shown in FIGS. 27A-52C, inclusive, and otherexamples used herein, are used merely to illustrate typical examples ofthe server addresses AQ_(n1) . . . AQ_(nm) (54) and results therefromthat may be possible. The examples shown in FIGS. 5A, 5B, and 6-10,11-26, and FIGS. 27A-52C, inclusive, and other examples used herein, areexamples of the substantially infinite variety of the server addressesAQ_(n1) . . . AQ_(nm) (54) that may be used with the client-servermultitasking system 10 of the present invention and the results that maybe obtained therefrom. The typical server addresses AQ_(n1) . . .AQ_(nm) (54), such as WebCrawler®, Altavista®, Lycos®, Infoseek®,Excite®, Yahoo®, LookSmart®, HotBot®, Dejanews®, Amazon®, Borders®,BarnesandNoble®, Google®, and/or others that may have been used hereinare for illustrative purposes only and are not intended to limit thescope of the client-server multitasking system 10 of the presentinvention.

It should also be obvious that the typical queries QQ_(n1) . . . QQ_(nm)(53) used in the examples shown in FIGS. 5A, 5B, and 6-10, 11-26, andFIGS. 27A-52C, inclusive, and other examples used herein are forillustrative purposes and are merely typical examples of thesubstantially infinite variety of the queries QQ_(n1) . . . QQ_(nm) (53)that may be used with the client-server multitasking system 10 of thepresent invention and the results that may be obtained therefrom, andare not intended to limit the substantially infinite variety of thequeries QQ_(n1) . . . QQ_(nm) (53) that may be used with theclient-server multitasking system 10 of the present invention and theresults that may be obtained therefrom. The typical queries QQ_(n1) . .. QQ_(nm) (53) used in the examples shown in FIGS. 5A, 5B, and 6-10,11-26, and FIGS. 27A-52C, inclusive, and other examples used herein arefor illustrative purposes only and are not intended to limit the scopeof the client-server multitasking system 10 of the present invention.

The typical labelled individual information groups LL_(n11) . . .LL_(n11) (86), the typical optional links LD_(nm1) . . . LD_(nmr) (82),and/or the typical optional descriptions DD_(nm1) . . . DD_(nmr) (83),and/or the typical optional prices/values PD_(nm1) . . . PD_(nmr) (84),and/or the typical optional images ID_(nm1) . . . ID_(nmr) (85), and/oradvertisements and/or advertisement links, and/or URL's, and/orlocations, and/or other items and/or objects shown in FIGS. 5A, 5B, and6-10, 11-26, and FIGS. 27A-52C, inclusive, and other examples usedherein are typical examples for illustrative purposes only and are notintended to limit the scope of the client-server multitasking system 10of the present invention. A substantially infinite variety of thelabelled individual information groups LL_(n11) . . . LL_(nzu) (86), theoptional links LD_(nm1) . . . LD_(nmr) (82), and/or the optionaldescriptions DD_(nm1) . . . DD_(nmr) (83), and/or the optionalprices/values PD_(nm1) . . . PD_(nmr) (84), and/or the optional imagesID_(nm1) . . . ID_(nmr) (85), and/or advertisements and/or advertisementlinks, and/or URL's, and/or locations, and/or other items and/or objectsmay result from the substantially infinite varieties and combinations ofthe queries QQ_(n1) . . . QQ_(nm) (53) and the substantially infinitevarieties and combinations of the server addresses AQ_(n1) . . . AQ_(nm)(54) of the client-server multitasking system 10 of the presentinvention, the client-server multitasking process 99, and themultitasking process 104, which in itself is a process.

Likewise, the typical grouping/sorting criteria shown herein in theexamples is for illustrative purposes only and is not intended to limitthe scope of the client-server multitasking system 10 of the presentinvention. It is possible to sort the responses within the serviceand/or information response, such as, for example, by category, query,group, page, order of importance, ascending and/or descending order,alphabetically and/or numerically, or other characteristics, asdetermined by the requestor, and/or the user, and/or the client-servermultitasking system, or to combine the responses within the serviceand/or information response, such as, for example, interleaving theresponses one with the other, such as, for example, by order ofrelevance or other parameters. The responses then are capable of beinggrouped by search criteria, server, order of importance, or by numericalfactors such as value, price, or other numerical quantifier. Theresponses may be presentable, for example, in ascending or descendingorder in interleaved format, such as top ones, twos, threes, and so on,or presentable separately to the requester and/or the user. The ordermay be order of importance or relevance related, or, for example,numerically valued, such as price or stock market value. A substantiallyinfinite variety of results may be generated from the substantiallyinfinite variety of grouping/sorting criteria possible with theclient-server multitasking system 10 of the present invention.

A substantially infinite variety of URL's, links, locations, sites,servers, and/or clients, other items and/or objects may be used with theclient-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and the multitasking process 104,which in itself is a process. Examples of URL's, links, locations,sites, servers, and/or clients, other items and/or objects shown inFIGS. 5A, 5B, and 6-52C, inclusive, are typical examples of URL's,links, locations, sites, servers, and/or clients, other items and/orobjects that may be of used with the client-server multitasking system10 of the present invention, the client-server multitasking process 99,and the multitasking process 104, and are used herein for illustrativepurposes only, and are not intended to limit the scope of theclient-server multitasking system 10 of the present invention, theclient-server multitasking process 99, and/or the multitasking process104.

A substantially infinite variety of advertisements and/or links may beused with the client-server multitasking system 10 of the presentinvention. The advertisements and/or links to such sites asNetscape®and/or “ABC News”®, Disney®, Discovery®, Warner®, ABC®,Universal®, CBS®, NBC®, “TV Guide”®, NYtimes®, ESPN®, WSjournal®, CNN®,and/or other sites used in the examples shown in FIGS. 5A, 5B, and 6-10,11-26, and FIGS. 27A-52C, inclusive, and other examples used herein arefor illustrative purposes only and are not intended to limit the scopeof the client-server multitasking system 10 of the present invention.

It should also be obvious that advertisements and/or links to such sitesas Netscape® and/or “ABC News”®, and/or other sites that may be usedherein are for illustrative purposes only and are not intended to limitthe scope of the client-server multitasking system 10 of the presentinvention.

Each of the typical service and/or information entry request formsIE_(n) at the user interface I_(n), which the user U_(n) may communicateother typical user input UI_(n) thereinto, may also have news stories,which may be updated intermittently on a substantially routine basis.

The client-server multitasking system and process are also capable ofperforming as a multiple query search engine, which performs multiplequeries of multiple sites, and performing as a single point of sale forpurchasing multiple products from multiple sources.

N. Additional Applications, Features, Uses, Embodiments, and Versions

Although the present invention has been described in considerable detailwith reference to certain preferred versions thereof, other versions arepossible. The present invention may be used in a variety ofapplications, which are not limited to those described herein.

The client-server multitasking system 10 of the present inventioncomprises a metasearch engine, which is a search engine that sends userrequests to several other search engines, servers, clients, and/ordatabases, and other suitable systems and/or devices, groups, sorts, andreturns the results from each one.

The client-server multitasking system 10, the client-server multitaskingprocess 99, the multitasking process 104, the search system and/orprocess, and/or the metasearch system and/or processes of the presentinvention may be used in a variety of searching, metasearching,ordering, shopping, and purchasing applications, and may alternativelyand/or hereinafter be referred to as the client-server multitaskingsystem 10/metasearch system, the client-server multitasking process99/metasearch process, and/or the multitasking process 104/metasearchprocess of the present invention.

FIGS. 1 and 2 show the client-server multitasking system 10/metasearchsystem of the present invention, having the requesters U₁ . . . U_(n)(12), also called the users U₁ . . . U_(n) (12), the corresponding userinterfaces I₁ . . . I_(n) (14), the corresponding clients C₁ . . . C_(n)(16), the server PS (18), the servers S₁ . . . S_(z) (20), and theoptional servers SO₁ . . . SO_(p) (22), constructed in accordance withthe present invention, which reside on the network 24. Each of the usersU₁ . . . U_(n) (12) communicate with the corresponding clients C₁ . . .C_(n) (16) through the corresponding user interfaces I₁ . . . I_(n)(14).

The client-server multitasking system 10/metasearch system may be usedto request, retrieve and organize information and/or data from multipledevices and/or multiple servers having multiple data streams, and groupand/or sort the information and/or data in real-time and on-the-fly,according to information in the user's request.

The client-server multitasking system 10/metasearch system of thepresent invention may be used to search or metasearch a single query orkeyword phrase of a plurality of sites substantially simultaneouslyand/or place one or a plurality of orders/purchases for the same and/ordifferent products or items substantially simultaneously.

The client-server multitasking system 10/metasearch system of thepresent invention may be used to search or metasearch a plurality ofqueries or keyword phrases of a plurality of sites substantiallysimultaneously and/or place one or a plurality of orders/purchases forthe same and/or different ones of products or items substantiallysimultaneously, and has a single point of purchase/sale option, toreceive and process orders from the users, based upon selections fromthe returned grouped and sorted results. The client-server multitaskingsystem 10/metasearch system may alternatively be instructed to placeorders and/or purchases automatically or semi-automatically, withoutuser intervention, based upon optional criteria.

For each request from each user, the client-server multitasking system10/metasearch system searches and/or requests information and/orservices from multiple sites, search engines, servers, databases, and/orclients substantially simultaneously. Each user may place multipleorders with multiple suppliers substantially simultaneously. Searchcriteria may be established by the users, which may comprise multiplequeries or keyword phrases and/or multiple site selection, and/or thesearch criteria, may be resident within the client-server multitaskingsystem 10/metasearch system. The sites, search engines, servers, and/orclients may be to be queried or to have the keyword phrases to be sentto may be chosen or selected by the users. Alternatively, optionaldefault search criteria and/or optional default sites, search engines,servers, and/or clients may be used.

The client-server multitasking system 10/metasearch system processesmultiple responses from the sites, search engines, servers, databases,and clients, and groups and sorts the results, all in real time andon-the-fly. Search criteria, grouping, sorting, and display criteria maybe established by the users and/or may be internal to the client-servermultitasking system 10/metasearch system. The client-server multitaskingsystem 10/metasearch system returns the grouped and sorted results tothe users.

The client-server multitasking system 10/metasearch system processes theorders, places the orders with third parties, and provides confirmationto the users, all in real time and on-the-fly.

The client-server multitasking system 10/metasearch system may haveadditional options, including spidering, advertisements, news bycategory, data storage, pay per click ads, automatic updating, automaticdata refreshing, and other options and other options, may be used on anykind of network, and in particular the internet, and process multiplerequests from multiple users substantially simultaneously.

FIG. 148 shows a simplified version of the particular service and/orinformation request IQ_(n) (28) being parsed, processed, and/orformatted into current request group QA_(nc) (50), request groupsQA_(n1) . . . QA_(nz) (51), and optional instructions VJ_(n1) . . .VJ_(nk) (52), and utilization of information therefrom to make therequests Q_(n1) . . . Q_(nm) (29), obtain the responses R_(n1) . . .R_(nm) (32), and incorporate information therefrom into the particularservice and/or information response IR_(n) (34). The current requestgroup QA_(nc) (50) may be any particular one the request groups QA_(n1). . . QA_(nz) (51).

FIG. 149 show yet a more simplified version of the particular serviceand/or information request IQ_(n) (28) being parsed, processed, and/orformatted into current request group QA_(nc) (50), request groupsQA_(n1) . . . QA_(nz) (51), and optional instructions VJ_(n1) . . .VJ_(nk) (52), and utilization of information therefrom to make therequests Q_(n1) . . . Q_(nm) (29), obtain the responses R_(n1) . . .R_(nm) (32), and incorporate information therefrom into the particularservice and/or information response IR_(n) (34). The current requestgroup QA_(nc) (50) may be any particular one the request groups QA_(n1). . . QA_(nz) (51), and is shown as the single request group QAnc (50),which may be selected by the user U_(n) (12), which may alternatively beset to default to the single request group QA_(nc) (50), and/or whichmay be resident in the server PS (18).

The client-server multitasking system 10 of the present inventioncomprises a metasearch engine, which is a search engine that sends userrequests to several other search engines, servers, clients, and/ordatabases, and other suitable systems and/or devices, groups, sorts, andreturns the results from each one.

In more detail, the client-server multitasking system 10/metasearchsystem of the present invention may be used to send user requests to andgroup, sort, and return results from each of the servers S₁ . . . S_(z)(20) and/or the optional servers SO₁ . . . SO_(p) (22), which maycomprise and/or be from the group consisting of: at least one serverdevice, at least one server, at least one search engine, at least onemetasearch engine, at least one database, at least one database server,at least one data server, at least one file server, at least oneinformation source, at least one site, at least one website, at leastone electronic communication network, at least one ECN, at least one ECNserver device, at least one ECN server, at least one ECN database, atleast one electronic trading system, at least one alternative tradingsystem, at least one computer assisted trading system, at least oneelectronic exchange, at least one electronic stock exchange, at leastone virtual exchange, at least one electronic market, at least oneelectronic stock market, at least one virtual market, at least oneclient device, at least one client, at least one process, at least onesoftware process, at least one program, at least one software program,at least one application, at least one software application, at leastone computer, at least one laptop computer, at least one personaldigital assistant, at least one peer-to-peer device, at least onepeer-to-peer application, at least one peer-to-peer softwareapplication, at least one communications device, at least onetransceiver, at least one wireless sensor node, at least one mote, atleast one wireless gateway node, at least one wireless computer, atleast one wireless platform, at least one robot, at least one wirelessrobot, at least one mobile server, at least one mobile device, at leastone cellular server, at least one cellular device, at least one cellularphone, at least one cell phone, at least one miniature computer, atleast one nanoscale server, at least one nanoscale computer, at leastone nanocomputer, at least one radio frequency identification device, atleast one newsgroup server, at least one e-mail server, at least onee-mail client, at least one intranet system, at least one personalsearch engine, at least one mobile search engine, at least onedirectory, at least one open directory, at least one web server, atleast one File Transfer Protocol (FTP) site, at least one FTP serverdevice, at least one FTP server, at least one podcast, at least onefeed, at least one feed aggregator, at least one feed reader, at leastone web feed, at least one webcast, at least one XML feed, at least onenewsfeed, at least one newsfeed server, at least one blog, at least oneRSS feed (Really Simple Syndication feed, Rich Site Summary feed, and/orResource Description Framework feed), at least one aggregator, at leastone feed aggregator, at least one feed reader, at least one webapplication, at least one video blog, at least one advertiser feed, atleast one advertiser server, at least one syndication server, at leastone web syndication server, at least one data stream device, at leastone multiple data stream device, at least one WiFi device, othersuitable systems and/or devices, and any combination thereof

Each of the clients C₁ . . . C_(n) (16) of the present invention maycomprise and/or be from the group consisting of: a client device, aclient, a server device, a server, a process, a program, a softwareprogram, an application, a software application, a computer, a laptopcomputer, a computer terminal, a communications device, a transceiver, apersonal digital assistant, a peer-to-peer device, a peer-to-peerapplication, a peer-to-peer software application, a wireless device, awireless computer, a wireless server, a wireless platform, a wirelessclient device, a wireless client, a mobile server, a mobile device, acellular server, a cellular device, a cellular phone, a cell phone, aminiature computer, a nanoscale server, a nanoscale computer, ananocomputer, a search engine, a metasearch engine, a site, a website, atelevision, a television device, a display device, an input-outputdevice, other suitable systems and/or devices, and any combinationthereof

Substantially any item can be ordered and/or purchased, using theclient-server multitasking system 10/metasearch system of the presentinvention, such as, for example, at least one item, at least oneproduct, at least one security, at least one stock, at least onecommodity, at least one currency, at least one financial product, atleast one financial instrument, at least one ticket, at least oneairline ticket, at least one service, information, data, music, audio,video, television, radio, at least on device, at least one apparatus, atleast one method, at least one process, data, at least one file, atleast one data file, at least one computer file, at least one musicfile, at least one video file, software, at least one application, atleast one software application, at least one item that can be purchased,at least one item for which an order can be placed, other suitableitems, and any combination of one or more thereof.

i. Brief Summary of Typical Applications

A brief summary of some typical examples of applications, features,uses, systems, embodiments, processes, and/or versions are listed and/ordescribed below, but the uses, applications, features, embodiments,systems, processes, and/or versions of the present invention are notlimited to those summarized, listed and/or described below.

Some features of the client-server multitasking system 10/metasearchsystem include:

-   -   searching multiple keyword phrases of multiple information        sources simultaneously, and grouping, and sorting results        according to the keyword phrases;    -   returning product and purchase information according to keyword        phrases and/or purchasing multiple products simultaneously;    -   making a single query or keyword search or multiple queries        and/or multiple keyword searches of multiple sites, search        engines, servers, databases, clients, information sources,        applications, software applications, programs, and/or software        programs substantially simultaneously, consolidating, grouping        and/or sorting search results, and as a single point of        purchasing and/or ordering one or more items;    -   searching or metasearching a single query or a plurality of        queries or keyword phrases of a plurality of sites, search        engines, servers, databases, clients, information sources,        applications, software applications, programs, and/or software        programs substantially simultaneously and/or placing one or a        plurality of orders/purchases for the same and/or different ones        of products or items substantially simultaneously;    -   querying and/or searching and/or spidering multiple sites,        search engines, servers, databases, clients, information        sources, applications, software applications, programs, and/or        software programs substantially simultaneously and/or obtaining        information and/or services from the multiple sites, search        engines, servers, databases, clients, information sources,        applications, software applications, programs, and/or software        programs; for each request from each user, the client-server        multitasking system 10/metasearch system searches, queries,        and/or requests information and/or services from multiple sites,        search engines, servers, databases, clients, information        sources, applications, software applications, programs, and/or        software programs substantially simultaneously;    -   multiple requests from multiple users may be processed        substantially simultaneously on substantially any kind of        network, and in particular the internet; each user may place        multiple orders with multiple suppliers substantially        simultaneously;    -   search criteria may be established by the users, which may        comprise multiple queries or keyword phrases and/or multiple        site selection, and/or the search criteria may be resident        within the client-server multitasking system 10/metasearch        system;    -   the sites, search engines, servers, databases, clients,        information sources, applications, software applications,        programs, and/or software programs to be searched may have the        queries, keyword phrases, search engines, servers, databases,        and/or clients chosen or selected by the users; alternatively,        optional default search criteria, display criteria, and/or        optional default sites, search engines, servers, databases,        clients, information sources, applications, software        applications, programs, and/or software programs may be used,        which may optionally be stored and/or resident within the        client-server multitasking system 10/metasearch system;    -   multiple responses from the multiple sites, search engines,        servers, databases, clients, information sources, applications,        software applications, programs, and/or software programs are        processed, grouped, and/or sorted into results, substantially        simultaneously, in real time and on-the-fly;    -   search criteria, grouping, sorting, and display criteria may be        established by the users and/or default values may be used        and/or may be internal to or resident within the client-server        multitasking system 10/metasearch system;    -   the client-server multitasking system 10/metasearch system may        be used to return the grouped and sorted results to the multiple        users, substantially simultaneously, in real time and        on-the-fly;    -   the client-server multitasking system 10/metasearch system may        have a single point of purchase/sale option, and receive and        process orders from the users, based upon selections from the        returned grouped and sorted results by the users and/or other        criteria, and may alternatively be instructed to place orders        and/or purchases automatically or semi-automatically, without        user intervention, based upon optional criteria;    -   orders may be processed and/or placed with third parties, and        users are provided with confirmation, all in real time and        on-the-fly;    -   additional options include spidering, advertisements, news by        category, data storage, pay per click ads, automatic updating,        automatic data refreshing, and other options.

Some applications of the client-server multitasking system 10/metasearchsystem include:

-   -   (a) business, corporate, and industrial systems and        applications; (b) business, government, and other types of        security/intelligence gathering systems; (c) specialized search        management systems; (d) scientific research, requiring multiple        simultaneous data acquisition and analysis capabilities; (e)        single point of purchase and single point of sale systems; (f)        the financial services industry and managed futures markets; (g)        commodities based systems and other systems having rapid,        dynamically changing environments; (h) internet related        systems; (i) the music and video industries; (j) homeland        security and military applications;    -   searching, grouping, sorting and/or identifying information        and/or services, shopping, placing, and confirming orders for        multiple products, financial instruments, stocks, commodities,        music, audio, video, television, searching grouping, sorting,        and/or identifying multiple data and/or data streams,        information and/or services, and/or files from the multiple        sites, search engines, servers, databases, clients, information        sources, applications, software applications, programs, and/or        software programs, substantially simultaneously;    -   search results and/or shopping results may be grouped according        to search query/keyword phrases and sorted in order selected by        the user or optionally according to default settings, which may        optionally be resident within the client-server multitasking        system 10/metasearch system and/or the clients;    -   grouped and/or sorted results may be supplemented by optional        spreadsheet applications, spread sheet programs, and/or        spreadsheet software;    -   news, intelligence, and information gathering from multiple        sources substantially simultaneously, consolidating, grouping,        sorting, and organizing results by category and/or other        criteria, using multiple queries/keyword phrases;    -   searching, querying, purchasing, selling, and/or combination        thereof in rapidly changing markets/environments and for        arbitrage, such as for commodities, stocks, financial        instruments, managed futures, and/or currency trading, and/or        any combination thereof, and particularly in commodities based        systems and other systems/markets having rapid, dynamically        changing environments;    -   parallel processing of multiple queries/keyword searches of        multiple information sources of the same and/or different types        and may be used on substantially any kind of network;    -   quick response intelligence gathering of multiple same and/or        different information requests of multiple sources, grouping and        sorting results substantially simultaneously in real time and        on-the-fly;    -   combined search and E-Commerce, and/or as a single point of        purchase/sale for multiple products in multiple categories from        multiple sites, and is particularly useful for corporate,        industrial, commercial, and government purchasing of multiple        products from multiple sources, as well as internet purchasing        of multiple products from multiple sources;    -   performing research, using multiple information sources,        multiple sites, search engines, servers, databases, clients,        applications, software applications, programs, and/or software        programs, and may be performed in parallel using multiple        queries/keyword phrases in multiple categories and/or multiple        fields substantially simultaneously, in real time, and        on-the-fly;    -   downloading multiple title/subject and/or        music/audio/video/television substantially simultaneously;    -   presenting results to single and/or multiple users substantially        simultaneously in real time and on-the-fly;    -   item/price comparisons, rapidly changing environments, real time        trend analyses, the financial services industry, managed        futures/arbitrage, business, commercial, and industrial        systems/applications, news, business and substantially all types        of intelligence gathering systems, and specialized search        management systems, such as intellectual property/patent search        management systems, libraries, and scientific research, in areas        such as bioinformatics, where multiple simultaneous data        acquisition and analysis capabilities/data mining would greatly        enhance and speed up diagnostics and/or benefit health based        systems;    -   point of purchase and point of sale for all types of corporate        purchasing systems and/or on premises shopping mall        enhancements; purchases may be made via on-line systems,        networks, intranets, the internet, and/or on-site shopping for        multiple product purchases from multiple stores/suppliers, for        example, in a shopping mall and/or other venue;    -   rapid response sale-purchasing system and/or a point of search,        purchase and sale for multiple products of multiple vendors at        the same and/or different sites with consolidation, grouping,        sorting, and item/price comparisons, in dynamic rapidly changing        environments; a single point of purchase system for multiple        product purchasing systems from multiple sources for corporate,        commercial, industrial, military, and logistics clients;    -   a global one stop shopping/purchasing system, as it becomes a        central point of sale/purchase, which can fulfill multiple        simultaneous same and/or different orders, directed to multiple        simultaneous same and/or different products, vendors/suppliers,        and sites with a single command (including a single credit card        entry) in multiple languages;    -   buyers/consumers can, for example, search for product        information and prices of vehicles, automobile windshields,        tires, television sets, and shoes, and buy one or more vehicles,        television sets, and pairs of shoes from multiple same and/or        different vendors at the same time, with a single command.    -   Homeland Security/quick response intelligence        gathering/anti-terrorist applications/military applications,        including multiple simultaneous data acquisition and analysis        capabilities, such as multiple database queries of facial        signatures, recognition, fingerprinting, signature analysis, and        identification systems, and multiple battlefield tactical and        strategic observation and analyses in real time;    -   applications in the music, entertainment, video, television,        videogame, game, and cable industries, internet sites, and/or        peer-to-peer systems, devices, programs, and/or applications for        acquisition of multiple music, video, game, audio, and/or        television titles from multiple sources in multiple song, video,        game, audio, and/or television categories, and for remarketing        to the public;    -   retrieval and organization of information and/or data from        multiple devices and/or multiple servers having multiple data        streams, and grouping and/or sorting of the information and/or        data in real-time and on-the-fly; information and/or data may be        grouped and/or sorted, according to information in the user's        request and/or data stream identifiers and/or other resident in        the client-server multitasking system 10.    -   A more detailed discussion of some typical examples of        applications, features, uses, systems, embodiments, processes,        and/or versions are listed and/or described below, but the uses,        applications, features, embodiments, systems, processes, and/or        versions of the present invention are not limited to those        summarized, listed and/or described below.        ii. Detailed Discussion

The present invention allows users to manage, communicate with, request,and obtain information and/or services from multiple sites, servers,and/or sources on virtually any kind of network or interconnectednetworks, in parallel, in real time, and on-the fly. The client-servermultitasking/metasearch technology performs multiple simultaneousrequests, retrieves, collects, formats, organizes, groups, and sortsresults from the same and/or different sites, clients and/or servers onvirtually any kind of network, substantially simultaneously, in realtime, and on-the-fly.

The client-server multitasking/metasearch technology may be used infinancial markets, business-to-business systems, business intelligence,news, data mining, search and database management systems, scientificresearch, global e-commerce, government and business intelligence andsecurity, research, analysis, on a global, macro, and micro scale, largeand small business applications, single point of purchase and sale ofmultiple products of multiple vendors at the same and/or different siteswith grouping, sorting, rank, and item/price comparisons, in dynamicrapidly changing environments, and other applications.

Applications include but are not limited to the Internet, Intranets,Global, Metropolitan, Wide, and Local Area Networks, multiple networks,network and multiple database management systems. The client-servermultitasking/metasearch technology may be used in: (a) business,corporate, and industrial systems and applications; (b) business, news,portals, and security/intelligence gathering systems; (c) the financialservices industry and managed futures/commodities markets; (d)government, homeland security, intelligence, military, and counterintelligence systems; (e) specialized search management systems, such asintellectual property/patent search management/pharmaceutical searchsystems; (f) scientific research, in areas such as bioinformatics,health, and DNA research, requiring multiple simultaneous dataacquisition and analysis capabilities; (g) single point of purchase andsingle point of sale systems; (h) systems having rapid, dynamicallychanging environments; (i) internet related systems, news, and portals;and (j) the music and video industries.

The client-server multitasking/metasearch system and process are capableof: parallel processing and management of the same and/or differentinformation and/or services from a variety of sources. The client-servermultitasking/metasearch system and process are capable of: making sameand/or different requests of the same and/or different ones of servers;retrieving information and/or services from the servers; collectingand/or sorting, grouping, and/or organizing responses therefrom; andcommunicating service and/or information responses to requesters and/orusers, all substantially simultaneously, in real time, and on-the-fly.

Users, clients, and systems may make multiple requests of multipleservers, databases, systems, and services, simultaneously and inparallel, and manage, group, and sort responses, in real time andon-the-fly. The requests may be the same and/or different one from theother, and may be in any order, for the same and/or different types ofinformation and/or services, the results being automatically managed,grouped and sorted, in accordance with characteristics dictated by theusers, clients, and systems.

The client-server multitasking/metasearch system is a quick responseintelligence gathering, purchasing and sales system that makes multiplequeries of multiple information sources substantially simultaneously,and optionally places buy and sell orders. A diverse crosscut of managedresults are grouped and sorted in real-time and on-the-fly into a singlegraphical user interface.

The client-server multitasking/metasearch system and process are capableof use on a variety of networks, such as global area networks, theinternet, metropolitan area networks, wide area networks, and local areanetworks, and are capable of communicating with, requesting informationand/or services therefrom, making requests of, querying, and searchingmultiple sites and types of sites, database management systems, searchengines and/or other sites, in combination one with the other,retrieving responses therefrom, and collecting, and/or sorting, groupingand/or organizing responses therefrom, in parallel, all substantiallysimultaneously, in real time, and on-the-fly.

Simple, easy to use, control panels and graphical user interfaces allowthe requesters and/or users to manage and control information, makerequests, and obtain results quickly and efficiently. The client-servermultitasking/metasearch system and process are capable of collecting,sorting, grouping, and/or organizing results from the servers, databasemanagement systems, search engines, and/or sites, in accordance withinstructions from the requesters, and/or users, and/or instructionsresident within the client-server multitasking/metasearch system and/orprocess.

The client-server multitasking/metasearch system and process are capableof use in a large variety of applications and industries, and arecapable of information comparison and/or trend analysis of informationfrom the same and/or different sources substantially simultaneously. Theclient-server multitasking/metasearch system is particularly useful indynamically changing environments. The client-servermultitasking/metasearch system and process are also optionally capableof creating, storing, building, and updating searchable databases frominformation retrieved, and searching the database alone or incombination with other systems and/or services.

BUSINESS, CORPORATE, HEALTH, AND INDUSTRY APPLICATIONS

The present invention may be applied to a number of business sectors,requiring the management of multiple services, information, and datasources.

The client-server multitasking/metasearch system and process act as aone-stop information, business intelligence, news, services, and datamanagement system, performing multiple simultaneous queries of multiplesimultaneous sites, databases and/or networks in parallel, specificallydedicated to particular industry and corporate needs. The use of thetechnology results in improved management of information, services, anddata, increased efficiency, significant reduction of time, decreasedmanpower requirements, and substantial cost savings.

News, business, and other types of intelligence may be gathered,grouped, sorted, and organized in multiple categories from multiple sameand/or different sources and types of sources, simultaneously, in realtime, on-the-fly, to supply corporate and industrial clients with themost recent up to date intelligence information in multiple specificfields of interest and in general, as well as internet based needs.

Pharmaceutical industry searches may be made of the National Instituteof Health, while simultaneously searching several public and/or privatedatabases, rather than sequentially searching each database, separately.Multiple simultaneous patent database searching, and parallel ratherthan sequential searching will result in significant improvements inefficiency, time, and cost savings in the intellectual property field,DNA, genetics, disease, and health research fields.

The present invention can perform as a one stop sales and purchasingsystem satisfying large corporate system needs. The client-servermultitasking/metasearch system and process may be used to evaluatemultiple supply sources by category, price, delivery dates, schedules,and other criteria simultaneously, and automatically make multiplepurchases in different categories simultaneously. Large automobilemanufacturers may license the technology as one stop purchasing systemsand/or logistics management systems, as the supply chain is commoditybased, having real time fluctuating prices and fluctuating availabilityof supply. Automobile manufacturers may obtain quotes on multipleproducts from multiple vendors, simultaneously, in real time andon-the-fly, required for the construction of one or more automobilemodels, sort and group the results by price and delivery schedule, andpurchase the products, either automatically, semi automatically, ormanually, in parallel, in real time, and on-the-fly.

The present invention may also be used in small office managementsystems, and may be used by internet based companies seeking to broadentheir businesses from typical internet portals and search sites. Theclient-server multitasking/metasearch system and process' single pointof sale system, which has a built in order processing system may also beused to fulfill internet based needs, providing item price comparisonshopping for multiple products from multiple suppliers, simultaneously.

Commodities and Rapidly Changing Markets

The client-server multitasking/metasearch system and process may be usedin rapidly changing markets, such as airline ticket comparison shopping,commodities markets of all types, from financial commodities, to thepurchase of oil, and beef, the financial services industry, applicationshaving real time multiple interactive information and/or serviceacquisition requirements, as well as multiple news, sports, weather, andother information feeds. The present invention may be used in multiplerapidly changing dynamic markets and environments, to make multiplequeries of multiple commodities and financial instruments in multiplemarkets, to place substantially simultaneous buy and sell orders inmultiple markets, and to evaluate the effects of simultaneously changingmultiple variables on desired results in real time.

Financial Markets

The present invention has direct applications to financial markets, andmore specifically, the managed futures, risk arbitrage and riskmanagement businesses. Risk arbitrage is an attempt to profit byexploiting price differentials of identical or similar financialinstruments, on different markets or in different forms, such assimultaneous comparison of several financial instruments in multiplemarkets, in addition to simultaneously comparing financial instrumentsin underlying markets, such as different options, strike prices andexchanges. The panacea would be multiple opposite transactions that takeplace simultaneously, generating profits with zero risk. Risk managementis the ability to view financial exposure based upon queries of multipledata streams, and return information in user friendly formats. Thesystem can also be used as a compliance monitor for clearing firms orother banking or financial institutions, where net capital computationsare required on a real-time basis.

Scientific Research

The client-server multitasking/metasearch system and process may be usedfor scientific research areas requiring multiple simultaneous dataacquisition and analysis capabilities, such as bioinformatics, whereparallel searching of multiple networks and databases will accelerateand provide results heretofore not possible.

Unique to the client-server multitasking/metasearch system and processis the ability to have a user input the criteria for which the userdesires results to be displayed, and prioritize the results by categoryin a variety of ways, within and external to groups,ascending/descending, price, numerical, alphabetical, and rank, etc.

Applications may also include the user of user defined multiple databasesources, which form a single data stream into a single user interfacefor simultaneously viewing multiple data sources.

Homeland Security/Intelligence Gathering

The client-server multitasking/metasearch system and process may beapplied to business and government security/intelligence gathering andanti-terrorist applications areas requiring multiple simultaneous dataacquisition and analysis capabilities, such as multiple databasequeries, using multiple keyword phrases, facial signatures, recognition,fingerprinting, signature analysis, and identification systems, whereparallel searching of multiple networks and databases for multipletargets will accelerate and provide results heretofore not possible.

The present invention may be applied to a number of security sectors,requiring the management of multiple services, information, and datasources, and, in particular, government, corporate and industry specifictools, requiring robust multiple client-server database managementsystems for both large and small business systems and applications.

The client-server multitasking/metasearch system and process can act asa one-stop information, services, and data management system, performingmultiple simultaneous queries of multiple simultaneous databases and/ornetworks in parallel, specifically dedicated to particular industry andcorporate needs. The use of the technology results in improvedmanagement of information, services, and data, increased efficiency,significant reductions of time, decreased manpower requirements, andsubstantial cost savings.

The technology may be directed to strategic and tactical security needsrequiring a quick response from multiple sources substantiallysimultaneously and on the fly. Homeland Security and otherclassified/unclassified sites, such as NLETS, NCIC, FBI, Interpol, ATF,U.S. Marshall, and Homeland Security systems and databases (users mustobtain all required security clearances) may be queried on a globalscale, and results of multiple queries of multiple threats and suspectswill be provided to users substantially simultaneously and on the fly.The latest continuously updated security news and alerts will also beprovided to users. Typical operational applications include airports,borders, ports, public venues, and the battlefield requiring quickresponse intelligence information to be collected from multiple globalsources, grouped, sorted, and provided to users in an easy to view andunderstand format for substantially simultaneous threat assessment.

Audio and Video Applications

The client-server multitasking/metasearch system and process may be usedin the music, video, and entertainment industry and selected internetsites, for acquisition of multiple music and video titles from multiplesources in multiple song and video categories, and for remarketing tothe public, as the next generation licensed napster.com and scour.comtype audio and video systems. Different music and video titles, genres,and artists may be requested and purchased from multiple sources, forexample, from the same and/or different sites, simultaneously and inparallel, affording users the ability to determine availability, pickand choose their best entertainment options, and order multiple itemsand types of items from multiple sources at the best prices,substantially simultaneously. The technology may also be used to providecontinuously, automatically, updated network and internet event andprogramming guides, such as real time type TV, gaming, chat group, andentertainment guides, applied to different network events and programs.

Search Engines

The present invention is capable of multiple simultaneous same and/ordifferent search queries, grouping, and sorting of results from the sameand/or different search engines and/or sites, all at the same time,on-the-fly, whereas, other Internet search engines are only capable ofsingle searches. The technology is capable of expanding the universe toan infinite number of simultaneous searches in multiple languages fordomestic and international markets, and being indexed on other searchengines.

Virtually anyone using the Internet and other networks, especially thosewho regularly have a need to perform several tasks simultaneously, canuse the client-server multitasking/metasearch system and process. Forexample, researchers can use the search capability to upgrade theirsearches by performing several searches in parallel, rather than,sequentially, and reduce research time.

The client-server multitasking/metasearch system and process isparticularly useful to address industries and entities with specializeddata mining requirements. The user controls the topics, the sites theuser searches, searches per group, url's per search, search time, datamining page and other characteristics. Users may control delivery ofresults, such as alternating interleaved results from each of the searchengines and/or sites, shopping sites, i.e. top ones, twos, threes, etc.,or separately and/or by category, grouping and sorting.

Since the searching that is performed may be incorporated into web sitesthat are dynamic, there is no great need for expensive, massive storagecapacity, and the information is always up to date. This differsradically from Internet portal search sites, such as Yahoo®, which arebasically cataloguing systems, some of which go out and “spider” theweb. It also differs from other metasearchers, which go out and returnthe first few results of a single search query of a few search engines.The client-server multitasking/metasearch system and process' uniquegraphical user interfaces facilitate and offer the user control inmaking multiple parallel searches of multiple sites, controlling,grouping, searching, and sorting the results in a user friendly manner.Default sites may also be used with the client-servermultitasking/metasearch system and process.

The technology is capable of simultaneously searching search engines,metasearchers, the Internet, and other networks in multiple languages;and can also store the resulting data and/or spider sites for creationof dedicated search engines and databases. The speed with which theclient-server multitasking/metasearch system and process is able toprocess and return dynamic data makes the present invention an extremelyimportant tool. In addition to unlimited multitasking and searchcapabilities, the client-server multitasking/metasearch system andprocess removes duplicates and returns clear concise results.

The present invention allows simultaneous searching of search engines,consumer product rating services, and shopping sites, including orderplacement. Typical scenarios allow users to simultaneously search sites,such as search engines, product rating organizations, such as ConsumerReports®, and shopping sites for multiple products, obtain ratings andassessments, place orders, and receive order confirmation in real time.

E-Commerce

The client-server multitasking/metasearch system and process' singlepoint of sale system, which has a built in order processing system, maybe used to fulfill internet based needs, providing item price comparisonshopping for multiple products from multiple suppliers, simultaneously.The present invention's global E-commerce system enables users tocomparison shop on-the-fly, performing price comparisons, productgrouping and/or vendor grouping, price sorting within groupings, andother comparisons of multiple simultaneous same and/or differentshopping sites in the same and/or different merchandise categories, fromthe same and/or different vendors, in multiple languages.

The technology also enables users to perform multiple productinformation searches and place multiple orders, simultaneously. Aconsumer can, thus, search, for example, consumer reports to obtainproduct information and place multiple product orders with multiplevendors of the user's choice, at the same time. The consumer can, forexample, search for product information and prices of television setsand shoes, and buy a television set and a pair of shoes from differentvendors at the same time. The system truly acts as a global one stopshop, as it becomes a central point of sale, which can fulfill multiplesimultaneous same and/or different orders, directed to multiplesimultaneous same and/or different products, and vendors/suppliers witha single command (including a single credit card entry) in multiplelanguages.

Broadband Applications

The client-server multitasking/metasearch system and process enablepeople and systems to manage resources, scan, find, and access neededinformation and services quickly, easily, and efficiently, especially asinternet, media, and other technologies converge. The technology has theability to correlate Internet and television programming with otherprogramming and/or media, as it becomes available, and integrate theresults. As broadband technology becomes more prevalent in homes andoffices, worldwide networks, cable TV and a host of other venues, willexpand broadcast programming on the Internet.

The present invention is capable of searching available programming fora set of parameters and/or keywords, and simultaneously correlating thekeywords with news stories. Financial institutions, for example, have aneed to watch multiple sources of news, markets, and/or other sources ofinformation, in order to become more profitable in their particularbusinesses. A user can, for example, enter the keyword “merger,” and/orother keywords, and if that word and/or words are used on a particularTV station and/or stations, and/or in an article or news story, theclient-server multitasking/metasearch system and process can retrievesuch sources of information and/or services substantiallysimultaneously, sort, and group, the information and/or services, andcommunicate the information and/or services to the user. A financialinstitution can, thus, for example, monitor many more sources and findopportunities that will increase its growth. The technology is alsoobviously beneficial for use in a variety of home and officeapplications.

Cross Platform and Wireless Devices

The present invention is applicable to multiple platforms, crossplatforms, and wireless devices. The technology may be used across anumber of platforms. The present invention may be used with virtuallyany kind of wireless system and/or platform, including wireless servers,wireless sensors, motes, wireless sensor networks (WSNs), wirelessrobotic servers and devices, mobile servers, Radio FrequencyIdentification (RFID) devices, mobile servers and devices, cellularservers and devices, sensor nodes, miniature, nanocomputers, andnansoscale servers and devices, wireless miniature devices,nanocomputers, and nansoscale servers and devices, and other wirelessdevices, and future wireless applications.

The present invention may be used to request, retrieve and organizeinformation and/or data from multiple wireless devices and/or multiplewireless servers having multiple data streams, and group and/or sort theinformation and/or data in real-time and on-the-fly, according toinformation in the user's request and/or data stream identifiers.

The present invention may also be used across platforms, includingsystems and browsers for interactive technology, which combinebroadcast, cable, satellite, Internet technology, internet television,WiFi, television applications, other future medium forms fordistribution of Internet, network and/or computer-based content,Wireless Application Protocol (WAP) enabled devices, cellulartelephones, wireless personal digital assistants (PDA's), other wirelessdevices, and other future wireless applications.

Additional Discussion of Financial Markets, Commodities and RapidlyChanging Markets

A stock market is a market for trading securities, including companystock and derivatives, which are typically listed and traded on a stockexchange or stock exchanges. Stock exchanges provide real-timeinformation on listed securities, and provide a marketplace (virtual orreal), which facilitate the exchange of securities between buyers andsellers. Various stock exchanges bring buyers and sellers of securities,stocks, derivatives, and other financial instruments together for thepurposes of trading. Derivatives may also be traded on a variety ofother markets. Bonds are still traditionally traded in an informal, overthe counter market, often referred to as the bond market. Commoditiesare traded on commodities markets. Other financial instruments may betraded on a variety of markets.

The size of the ‘stock market’ is estimated to be approximately $51trillion. The world derivatives market is estimated to be about $480trillion, and the worldwide ‘bond market’ is estimated at $45 trillion.

The stock market in the United States includes the trading of allsecurities listed on the New York Stock Exchange (NYSE)®, the AmericanStock Exchange (AMEX)®, National Association of Securities DealersAutomated Quotations system (NASDAQ)®, as well as on many regionalexchanges, the Over The Counter Bulletin Board (OTCBB)®, and the PinkSheets®, which is an electronic quotation system that displays quotesfrom broker dealers for many over-the-counter traded securities.European examples of stock exchanges include the Paris Bourse®(now partof, Euronext®, which is a pan-European stock exchange based in Paris,with subsidiaries in Belgium, France, the Netherlands, Portugal, and theUnited Kingdom), the London Stock Exchange (LSE)®, and the DeutcheBorse®. It should be noted that the NYSE Group®merged with Euronext®inApril, 2007 to form the first global equities exchange.

Participants in the stock market range from small individual stockinvestors to large hedge fund traders, who can be based anywhere. Ordersare usually executed by a professional at a stock exchange.

Some exchanges have physical locations, where transactions are carriedout on trading floors. Other types of exchange are virtual exchanges,composed of a network or networks of computers, where trades are madeelectronically via traders at computer terminals.

Actual trades are based on an auction market paradigm, in which, forexample, a potential buyer bids a specific price for a stock, and apotential seller asks a specific price for the stock. When the bid andask prices match, a sale takes place on a first come first served basis,if there are multiple bidders or askers at a given price.

The New York Stock Exchange® is a physical exchange, and is also a“listed” exchange, because only stocks listed with the exchange may betraded. Orders enter via brokerage firms that are members of theexchange and flow down to floor brokers, who go to specific locations,called trading posts, on the floor, where the stock or stocks trade. Ateach of the trading posts, there are specific individuals, known asspecialists, who match buy and sell orders, using an auction methodknown as “open outcry,” in which traders may enter “verbal” bids andoffers. The current bid price is the highest amount any buyer is willingto pay, and the current ask price is the lowest price at which someoneis willing to sell. For a trade to take place, there must be a matchingbid and ask price. If there is a spread, which is the difference betweenthe price available for an immediate sale (bid) and an immediatepurchase (ask/offer), no trade takes place, although the specialist issupposed to use his own resources of money or stock to close thedifference, after some time. Once a trade takes place, details of thetrade are reported on the “tape”, and sent back to the brokerage firmthat placed the order. The brokerage firm then notifies the investor whoplaced the order that the trade has taken place and the price of thetrade.

The NASDAQ®, on the other hand, is a virtual (listed) exchange, whereall trading is performed over a computer network, which is similar totrading on a physical exchange, in that the seller provides an askingprice, and the buyer provides a bidding price. However, buyers andsellers are electronically matched. One or more NASDAQ®market makersalways provides a bid and ask price at which they will always purchaseor sell ‘their’ stock. The market maker is typically a firm that quotesboth a buy and a sell price in a financial instrument or commodity,hoping to make a profit on a ‘turn’ or bid/offer spread.

The Paris Bourse®, now part of Euronext®is an order-driven, electronicstock exchange, which was automated in the late 1980s, which prior tothat time was an open outcry exchange in which stock brokers met on thetrading floor. In 1986, however, the Paris Bourse® adopted a ComputerAssisted Trading System (CATS) developed for the Toronto Stock Exchange®in 1977, and the order matching process was fully automated. Since thattime, many exchanges have shifted to electronic trading.

Computers and electronic trading have decreased or eliminated the needfor physical trading floors, and the balance of power has shifted toelectronic markets, with more and more electronic trading taking place.All of the above orders could be entered into an electronic market,although simple market and limit orders are generally encouraged byorder priority rules. A market order is a buy or sell order to beexecuted by a broker immediately at current market prices, and as longas there are willing sellers and buyers, a market order will be filled.A limit order is an order to buy a security at no more (or sell at noless) than a specific price, which gives a customer some control overthe price at which a trade is executed, but may prevent the order frombeing executed (“filled”).

An electronic communication network (ECN), as understood and currentlyused in financial circles, is a type of computer system that facilitatestrading of financial products outside of stock exchanges. The primaryproducts that are traded on ECNs are stocks and currencies, althoughother suitable products and/or financial instruments may be traded onECNs. For the most part, ECNs came into existence in 1998, when theSecurities and Exchange Commission (SEC) authorized their creation.However, the first true ECN was the NASDAQ over-the-counter quotationsystem, created by the National Association of Securities Dealers(NASD)®in 1971.

Electronic communication networks (ECNs) are commonly known asAlternative Trading Systems (ATS). The Securities and ExchangeCommission has defined an ECN as any electronic system that widelydisseminates to third parties orders entered into it by an exchangemarket maker or over-the-counter (“OTC”) market maker, and permits suchorders to be executed in whole or in part.

A 1969 an American Stock Exchange (AMEX)(g study estimated that errorsin hand written securities order processing cost brokerage firmsapproximately $100 million per year. The NASDAQ system automated suchorder processing, and provided brokers with the latest competitive pricequotes via a computer terminal, in order to overcome such problems.Later, more advanced ECNs were developed, as a result of regulatorychanges, resulting from a 1994 United States Justice Departmentinvestigation of possible antitrust violations by NASDAQ® itself.NASDAQ® adopted new order handling rules that integrated ECNs into theNASDAQ® system, as part a settlement relating to the antitrust charges.The Securities and Exchange Commission (SEC) adopted Regulation ATS,after the settlement, which permitted ECNs the option to register asstock exchanges or else to be regulated under a separate set ofstandards for ECNs.

Major ECNs that became active at that time were Instinet® and Island®(part of Instinet® was spun off and merged with Island® into INET®, andacquired by NASDAQ®), Archipelago Exchange®, and Brut® (now acquired byNASDAQ®). The Archipelago Exchange® is an entirely online securitiesexchange on which both stocks and options are traded, which was acquiredby the New York Stock Exchange®, and which is currently owned by NYSEEuronext®, which merged with Archipelago Holdings® in a reverse mergerin early 2006.

For stock, ECNs exist as a class of Securities and Exchange Commission(SEC) permitted Alternative Trading Systems (ATS). ECNs are also usedfor currency trading. By trading through an ECN, a currency tradergenerally gets a better price than trading by voice over the phone.Other benefits are greater price transparency, faster processing,increased liquidity and more availability in the marketplace. Banks alsolower their costs as there is less manual involvement.

In order to trade with an ECN, one must be a subscriber to the ECN. ECNsubscribers can enter orders into the ECN via a custom computer terminalor network protocols. The ECN then matches contra-side orders (i.e. asell-order is “contra-side” to a buy-order with the same price and sharecount) for execution. The ECN posts unmatched orders on the system forother subscribers to view. Generally, buyers and sellers are anonymous,with the trade execution report listing the ECN as the party to thetransaction

ECNs increase competition among trading firms by lowering transactioncosts, giving clients full access to their order books, and offeringorder matching outside of traditional exchange hours. The technologyused for ECNs, Alternative Trading Systems (ATS), electronic tradingsystems, and the like is expected to spread to electronic markets andmarkets of all kinds and types. The present invention is intended toinclude all such electronic markets, electronic trading systems,markets, and the like.

An “order book” refers to the system operated by many stock exchangesand other exchanges for storing and matching the various kinds of orders(such as limit orders and/or market orders) that can be placed on suchexchanges. The order book for the financial instrument being traded istypically displayed to the subscriber on a computer terminal, on whichthe subscriber may place an order.

The client-server multitasking system 10/metasearch system of thepresent invention may be used to request, retrieve and organizeinformation and/or data from a plurality of ECNs, and group and/or sortthe information and/or data in real-time and on-the-fly, according toinformation in the user's request and/or instructions resident in theclient-server multitasking system 10/metasearch system. Theclient-server multitasking system 10/metasearch system may be used togroup and/or sort information into a plurality of order books, eachorder book for a different financial instrument, security, and/or stock.Users may place orders for the financial instruments, securities, and/orstock.

Again, FIGS. 1 and 2 show the client-server multitasking system10/metasearch system of the present invention, having the requesters U₁. . . U_(n) (12), also called the users U₁ . . . U_(n) (12), thecorresponding user interfaces I₁ . . . I_(n) (14), the correspondingclients C₁ . . . C_(n) (16), the server PS (18), the servers S₁ . . .S_(z) (20), and the optional servers SO₁ . . . SO_(p) (22), constructedin accordance with the present invention, which reside on the network24. Each of the users U₁ . . . U_(n) (12) communicate with thecorresponding clients C₁ . . . C_(n) (16) through the corresponding userinterfaces I₁ . . . I_(n) (14).

Again, the user U_(n) (12) enters the corresponding user input UI_(n)(25) having one or more of the same and/or different user requests qu₁₁. . . qu_(nu) (26) into the corresponding user interface I_(n) (14), asshown in FIG. 3. The user requests qu₁₁ . . . qu_(nu) (26) arecommunicated from the user interface I_(n) (14) to the correspondingclient C_(n) (16) within the corresponding user service and/orinformation request iq_(n) (27), having the user requests qu₁₁ . . .qu_(nu) (26) and other optional information. The user U_(n) (12) mayenter the corresponding user input UI_(n) (25) at the same and/ordifferent times.

Now again, the user interface I_(n) (14) communicates the user serviceand/or information request iq_(n) (27) to the corresponding client C_(n)(16), which optionally formats the corresponding user service and/orinformation request iq_(n) (27) into the corresponding service and/orinformation request IQ_(n) (28), as required. The service and/orinformation requests IQ_(n) (28) has information therein that may beused to formulate one or more of the same and/or different requests Q₁₁. . . Q_(nm) (29) to be made of one or more of the same and/or differentones of the servers S₁ . . . S_(z) (20), referred to by the serverdesignations S₁₁ . . . S_(nm) (30), in accordance with a designationscheme which designates the servers S₁ . . . S_(z) (20) to becommunicated with corresponding to the requests Q₁₁ . . . Q_(nm) (29) asthe corresponding server designations S₁₁ . . . S_(nm) (30), as shown inFIGS. 2 and 4. FIG. 4 shows the server designations S₁₁ . . . S_(nm)(30) for typical ones of the requests Q₁₁ . . . Q_(nm) (29) and atypical one of the servers Sz (20). Each of the requests Q₁₁ . . .Q_(nm) (29) may be the same and/or different one from the other and maybe made of the same and/or different ones of the servers S₁ . . . S_(z)(20) at the same time and/or different times.

Again, in more detail, the client C_(n) (16) formats the service and/orinformation response IR_(n) (34) into the corresponding user serviceand/or information response ir_(n) (36), as required, and communicatesthe user service and/or information responses ir_(n) (36) to thecorresponding user interface I_(n) (14). The user interface I_(n) (14)incorporates the user service and/or information responses ir_(n) (36)into the corresponding user responses UR_(n) (37), which is derived atthe user interfaces I_(n) (14), and communicated by the user interfaceI_(n) (14) to the corresponding user U_(n) (12) (See FIG. 2). The userU_(n) (12) reviews the corresponding user response UR_(n) (37) at theuser interfaces I_(n) (14) and/or selects additional services and/orinformation therefrom, such as, for example, placing an order for one ormore securities.

Now again, in more detail, the service and/or information responsesIR_(n) (34) has the parsed, processed, formatted, sorted, grouped,and/or organized service and/or information group G_(n) (35) having thequery information groups GI_(n1) . . . GI_(nz) (63) therein, resultingfrom the same and/or different ones of the typical queries QQ_(n1) . . .QQ_(nm) (53) having been sent to the same and/or different ones of thetypical server addresses AQ_(n1) . . . AQ_(nm) (54). Each of the queryinformation groups GI_(n1) . . . GI_(nz) (63) may have the servicesand/or information therein optionally parsed, processed, formatted,sorted, grouped, and/or organized according to sorting/grouping criteriaspecified in the typical optional instructions VJ_(n1) . . . VJ_(nk)(52) by the user U_(n) (12), and/or according default instructionsand/or according to other information resident within the server PS(18).

FIGS. 148 and 149 show simplified versions of the particular serviceand/or information request IQ_(n) (28) being parsed, processed, and/orformatted into the current request group QA_(nc) (50), and utilizationof information therefrom to make the requests Q_(n1) . . . Q_(nm) (29),obtain the responses R_(n1) . . . R_(nm) (32), parse, process, format,group, sort, and/or organize the service and/or information group G_(n)(35) having the query information groups GI_(n1) . . . GI_(nz) (63)therein, and incorporate information therefrom into the particularservice and/or information response IR_(n) (34).

The query information groups GI_(n1) . . . GI_(nz) (63) associated witha typical securities transaction may comprise a plurality of order booksOB_(n1) . . . OB_(nz) (410), in accordance with the present invention.

FIG. 150 shows the service and/or information group G_(n) (35)associated with a typical securities transaction. The query informationgroups GI_(n1) . . . GI_(nz) (63) are represented as the plurality oforder books OB_(n1) . . . OB_(nz) (410) for a plurality of securities,stocks, financial products, financial instruments, stocks, commodities,and/or currencies, resulting from the user service and/or informationrequest iq_(n) (27) being executed by the user U_(n) (12) at the userinterface I_(n) (14), in accordance with the present invention.

Now, again, the query information groups GI_(n1) . . . GI_(nz) (63)comprise the plurality of order books OB_(n1) . . . OB_(nz) (410) forthe plurality of securities, stocks, financial products, financialinstruments, stocks, commodities, and/or currencies, and are representedin FIG. 150 as the plurality of order books OB_(n1) . . . OB_(nz) (410)for the plurality of securities, stocks, financial products, financialinstruments, stocks, commodities, and/or currencies.

Each of the queries QQ_(n1) . . . QQ_(nm) (53) typically comprises akeyword phrase, comprising at least one keyword, indicia, or symbol,which signifies the security for which each respective one of theplurality of order books OB_(n1) . . . OB_(nz) (410) is to be returned,and which are shown in FIG. 150.

Typical market data is shown in FIG. 150 for the order books OB_(n1) . .. OB_(nz) (410) for Exxon (XOM)®, IBM (IBM)®, and Bank of America(BAC)®, resulting from the queries QQ_(n1) . . . QQ_(nm) (53), whichtypically comprise the keyword phrases XOM®, IBM®, and BAC®, and whichsignify the securities for which the order books are to be displayed,although other suitable keyword phrases, indicia, symbols, and/or acombination thereof may be used.

The plurality of order books OB_(n1) . . . OB_(nz) (410) have namesNM_(n1) . . . NM_(nz) (412) of the securities and other identifiersID_(n1) . . . ID_(nz) (414), such as keyword phrases, indicia, symbols,and/or a combination thereof, in this case the ticker symbol, thatidentifies for which security that the market data of the respectiveplurality of order books OB_(n1) . . . OB_(nz) (410) is for. FIG. 150shows market data for Exxon®, IBM®, and Bank of America®, each of theplurality of order books OB_(n1) . . . OB_(nz) (410) typically beingdifferent from each other. In order to trade with an ECN, the user U_(n)(12) must typically be a subscriber to the ECN.

Last trade prices TD_(n1) . . . TD_(nz) (416), indicia ND_(n1) . . .ND_(nz) (418), in this case arrows or other suitable indicia, indicatingthe current movement of the highest bid, net changes NC_(n1) . . .NC_(nz) (420) of the last trade prices with respect to yesterday'sclosing prices, volumes VL_(n1) . . . VL_(nz) (422) of the last trades,high trade prices for the day HH_(n1) . . . HH_(nz) (424), low tradeprices for the day LW_(n1) . . . LW_(nz) (426), and the total volumestraded for the day VT_(n1) . . . VT_(nz) (428) are also shown in FIG.150 for each of the securities.

The plurality of order books OB_(n1) . . . OB_(nz) (410) comprise biddata BD_(n1) . . . BD_(nz) (430) and offer data OD_(n1) . . . OD_(nz)(432) for each of the securities, as shown in FIG. 150. The bid dataBD_(n1) . . . BD_(nz) (430) is sorted in descending order according tobid price DP_(n1) . . . DP_(nz) (434). The offer data OD_(n1) . . .OD_(nz) (432) is sorted in ascending order according to offer priceAP_(n1) . . . AP_(nz) (436).

The bid data BD_(n1) . . . BD_(nz) (430) and the offer data OD_(n1) . .. OD_(nz) (432) comprise a plurality of bid quotes QB_(n11) . . .QB_(nzx) (438) and a plurality of offer quotes QO_(n11) . . . QO_(nzx)(440), respectively, for each of the plurality of order books OB_(n1) .. . OB_(nz) (410). Each of the bid quotes QB_(n11) . . . QB_(nzx) (438)and each of the offer quotes QO_(n11) . . . QO_(nzx) (440) comprisevolume in hundreds (100's) of shares 442, an identifier 444, in thiscase a four character identifier, that identifies the ECN or marketmaker of the security (the identifier 444 may be a keyword phrase,indicia, or symbol or other suitable identifier), and the bid priceDP_(n1) . . . DP_(nz) (434) or the offer price AP_(n1) . . . AP_(nz)(436). An identifier 446, which may be an asterisk (*) or other suitableidentifier, shows the most recently updated quote for each of theplurality of order books OB_(n1) . . . OB_(nz) (410).

A plurality of optional order entry boxes OE_(n1) . . . OE_(nz) (448)and OG_(n1) . . . OG_(nz) (450) are also shown in each of the pluralityof order books OB_(n1) . . . OB_(nz) (410), which allows the user U_(n)(12) to place a plurality of bids and/or offers, respectively, for anyand/or all of the plurality of securities, stocks, financial products,financial instruments, stocks, commodities, and/or currencies shown inthe plurality of order books OB_(n1) . . . OB_(nz) (410), by enteringsuitable bid and/or order information. The user U_(n) (12) mayoptionally also place a plurality of bids and/or offers for any and/orall of the plurality of securities, stocks, financial products,financial instruments, stocks, commodities, and/or currencies shown inthe plurality of order books OB_(n1) . . . OB_(nz) (410) by highlightingthe particular bid data BD_(n1) . . . BD_(nz) (430) and/or the offerdata OD_(n1) . . . OD_(nz) (432) for the plurality of securities,stocks, financial products, financial instruments, stocks, commodities,and/or currencies shown in FIG. 150 and clicking on the highlighted biddata BD_(n1) . . . BD_(nz) (430) and/or the highlighted offer dataOD_(n1) . . . OD_(nz) (432) with a mouse or other suitable tool. Theplurality of bids and/or offers may alternatively be entered on aseparate graphical user interface.

FIG. 150 shows the plurality of order books OB_(n1) . . . OB_(nz) (410)for securities, although other suitable financial products, financialinstruments, stocks, commodities, currencies, and/or combinationsthereof may be used.

The query information groups GI_(n1) . . . GI_(nz) (63) associated witha typical securities transaction may comprise a plurality of order booksOB_(n1) . . . OB_(nz) (410), in accordance with the present invention,as shown in FIG. 150, or, alternatively, the query information groupsGI_(nz) (63) associated with another typical securities transaction maycomprise a single order book OB_(nz) (410), as shown in FIG. 151, inaccordance with the present invention.

The user U_(n) (12) may optionally enter one or more orders into anysingle order book OB_(nz) (410) or plurality of order books OB_(n1) . .. OB_(nz) (410). The order and/or orders may be, for example, forproducts, items, financial products, financial instruments, stocks,commodities, currencies, orders, purchases, and/or instructions, and/orpayment, and/or other information and/or services to be directed toand/or requested of third parties, and/or combinations thereof. Theorder and/or orders may be placed, for example, with the servers S₁ . .. S_(z) (20) and/or the optional servers SO₁ . . . SO_(p) (22), any ofwhich may be ECNs, other suitable parties and/or third parties, and/orother ones of the clients C₁ . . . C_(n) (16) through the server PS (18)and/or the client C_(n) (16). The order and/or orders may, thus, beplaced through and by the server PS (18) and/or the client C_(n) (16),eliminating the need for the user U_(n) (12) to place one or moreseparate ones of the orders with the third parties, ECNs, the servers S₁. . . S_(z) (20) and/or the optional servers SO₁ . . . SO_(p) (22)separately and/or individually.

FIG. 150 shows a particular service and/or information group G_(n) (35)associated with a typical securities transaction, showing queryinformation groups GI_(n1) . . . GI_(nz) (63) represented as a pluralityof order books OB_(n1) . . . OB_(nz) (410) at the user interfaces I_(n)(14) for a plurality of securities, stocks, financial products,financial instruments, stocks, commodities, and/or currencies; and FIG.151 shows a particular service and/or information group G_(n) (35)associated with a typical securities transaction, showing the queryinformation group GI_(nz) (63) represented as the order book OB_(nz)(410) at the user interface I_(n) (14) for a security, stock, financialproduct, financial instrument, commodity, and/or currency.

The order books OB_(n1) . . . OB_(nz) (410) at the user interfaces I_(n)(14) of FIG. 150 and/or the order book OB_(nz) (410) at the userinterface I_(n) (14) of FIG. 151 may be used as an order form or orderforms, which provide direct placement of orders and/or confirmation oforders and/or purchases with the servers S₁ . . . S_(z) (20) and/or theoptional servers SO₁ . . . SO_(p) (22), and/or ECNs, and/or thirdparties that reside on the network 24. The user U_(n) (12) may enter theorder placement into the user interface I_(n) (14) through the userinput UI_(n) (25), and receive order confirmation through the userinterface I_(n) (14). The client C_(n) (16) may communicate the orderplacement from the user interface I_(n) (14) to the server PS (18),which may communicate the order placement to the servers S₁ . . . S_(z)(20) and/or the optional servers SO₁ . . . SO_(p) (22) and/or the ECNsand/or the third parties. The server PS (18) may alternatively and/oradditionally communicate the order confirmation received from theservers S₁ . . . S_(z) (20) and/or the optional servers SO₁ . . . SO_(p)(22) and/or the ECNs and/or the third parties to the client C_(n) (16),which may communicate the order confirmation to the user interface I_(n)(14) for presentation to the user U_(n) (12). The order placement and/orthe order confirmation may be stored within the server PS (18) and/orthe client C_(n) (16). The order placement and/or the order confirmationis typically secure, and may be encrypted, and is typically communicatedusing secure communications means.

FIG. 151 shows the service and/or information group G_(n) (35)associated with another typical securities transaction, in which, forexample, one or more transactions are conducted for a single security,stock, financial product, financial instrument, commodity, and/orcurrency. The query information groups GI_(n1) (63) are represented asthe order books OB_(nz) (410) for the security, stock, financialproduct, financial instrument, commodity, and/or currency, resultingfrom the user service and/or information request iq_(n) (27) beingexecuted by the user U_(n) (12) at the user interface I_(n) (14).

The optional order entry boxes OE_(nz) (448) and OG_(nz) (450) shown inthe order book OB_(nz) (410) allow the user U_(n) (12) to place one ormore bids and/or offers, respectively, for a security, stock, financialproduct, financial instrument, commodity, and/or currency, by enteringsuitable bid and/or order information. One or more bids and/or offersmay be made substantially simultaneously, using the optional order entryboxes OE_(nz) (448) and OG_(nz) (450).

The optional order entry boxes OE_(nz) (448) comprise a plurality of bidvolume entry boxes 460, a plurality of bid price entry boxes 462, and aplurality of bid ECN identifier boxes 464 that identify the ECN ormarket maker of the security for which a bid or bids are may be made.Volume, bid price, and ECN may be entered into the bid volume entryboxes 460, the bid price entry boxes 462, and the bid ECN identifierboxes 464, respectively to place one or more bid orders substantiallysimultaneously. One or more bid orders may be entered into the optionalorder entry boxes OE_(nz) (448), by entering bid volume, bid price, andECN into the respective bid volume entry boxes 460, the bid price entryboxes 462, and the bid ECN identifier boxes 464, to place one or morebid orders, respectively, substantially simultaneously.

The optional order entry boxes OG_(nz) (450) comprise a plurality ofoffer volume entry boxes 470, a plurality of offer price entry boxes472, and a plurality of offer ECN identifier boxes 474 that identify theECN or market maker of the security for which an offer or offers may bemade. Volume, offer price, and ECN may be entered into the offer volumeentry boxes 470, the offer price entry boxes 472, and the offer ECNidentifier boxes 474, respectively to place one or more offer orderssubstantially simultaneously. One or more offer orders may be enteredinto the optional order entry boxes OG_(nz) (450), by entering offervolume, offer price, and ECN into the respective offer volume entryboxes 470, the offer price entry boxes 472, and the offer ECN identifierboxes 474, to place one or more offer orders, respectively,substantially simultaneously.

Both bid orders and/or offer orders may be made substantiallysimultaneously and/or separately, as required.

The user U_(n) (12) may optionally alternatively and/or additionallyplace bids and/or offers for one or more of the security, stock,financial product, financial instrument, commodity, and/or currencyshown in the order book OB_(nz) (410) by highlighting the particular biddata BD_(n1) . . . BD_(nz) (430) and/or the offer data OD_(n1) . . .OD_(nz) (432) for the security, stock, financial product, financialinstrument, stock, commodity, and/or currency, and highlighting and/orclicking on the bid data BD_(n1) . . . BD_(nz) (430) and/or the offerdata OD_(n1) . . . OD_(nz) (432) with a mouse or other suitable tool,and/or using a keyboard or other suitable tool for order entry and/ororder placement.

Alternatively and/or additionally bid volume and/or offer volume may beentered into one or more bid volume entry boxes 482 and/or one or moreoffer volume entry boxes 484 adjacent respective ones of the bid quotesQB_(n11) . . . QB_(nzx) (438) and/or the offer quotes QO_(n11) . . .QO_(nzx) (440), to place one or more bid orders and/or one or more offerorders, respectively, substantially simultaneously. Bid orders and/oroffer orders may be made by highlighting and/or clicking on the bidvolume entry boxes 482 and/or the offer data offer volume entry boxes484 with a mouse or other suitable tool, and/or using a keyboard orother suitable tool for order entry and/or order placement.

One or more bid orders and/or one or more offer orders may be madesubstantially simultaneously and/or separately, as required.

Bid orders and/or offer orders may alternatively and/or additionally beentered and/or placed by highlighting and clicking on Bid order box 476,Offer order box 478, and or Submit box 480 with a mouse or othersuitable tool, and/or using a keyboard or other suitable tool for orderentry and/or placement

The bid orders and/or offer orders may alternatively be entered and/orplaced, using any other suitable or separate graphical user interface.

The bid volume entry boxes 482 and/or the offer volume entry boxes 484adjacent respective ones of the bid quotes QB_(n11) . . . QB_(nzx) (438)and/or the offer quotes QO_(n11) . . . QO_(nzx) (440) may be used toplace one or more bid orders and/or one or more offer orders,respectively, substantially simultaneously, for one or a plurality ofsecurities, stocks, financial products, financial instruments, stocks,commodities, and/or currencies, as shown in FIGS. 150 and 151 fortypical ones of securities, stocks, financial products, financialinstruments, stocks, commodities, and/or currencies.

The optional order entry boxes OE_(nz) (448), comprising the bid volumeentry boxes 460, the bid price entry boxes 462, and the bid ECNidentifier boxes 464, and/or the optional order entry boxes OG_(nz)(450), comprising the offer volume entry boxes 470, the offer priceentry boxes 472, and the offer ECN identifier boxes 474, mayalternatively and/or additionally be used to place one or more bidorders and/or one or more offer orders, respectively, substantiallysimultaneously, for one or a plurality of securities, stocks, financialproducts, financial instruments, stocks, commodities, and/or currencies,as shown in FIGS. 150 and 151 for typical ones of securities, stocks,financial products, financial instruments, stocks, commodities, and/orcurrencies. Each of the bid orders and/or the offer orders may typicallybe placed directly with the appropriate ECNs without the need foradditional steps, additional clicks and/or click-throughs, and/or use ofadditional screens and/or user interfaces. The Bid order box 476, theOffer order box 478, and/or the Submit box 480 may optionally be used toenter and/or place orders for one or a plurality of securities, stocks,financial products, financial instruments, stocks, commodities, and/orcurrencies.

FIG. 151 shows the order book OB_(nz) (410) for a security, althoughother suitable financial products, financial instruments, stocks,commodities, currencies, and/or combinations thereof may be used.

Again, the client-server multitasking system 10/metasearch system of thepresent invention may be used to search or metasearch a single query orkeyword phrase of a plurality of sites and/or ECNs substantiallysimultaneously and/or place one or a plurality of orders/purchases forthe same and/or different securities, stocks, financial products,financial instruments, stocks, commodities, and/or currencies, or itemssubstantially simultaneously.

Now, again, the client-server multitasking system 10/metasearch systemmay be used to make a single query or keyword search or multiple queriesand/or multiple keyword searches of multiple sites, search engines,servers, ECNs, databases, clients, information sources, applications,software applications, programs, and/or software programs substantiallysimultaneously, consolidating, grouping and/or sorting search results,and as a single point of purchasing and/or placing and/or ordering oneor more items.

A partial list of present and past ECNs, some of which have beenincluded in FIGS. 150 and 151, includes: ARCA: Archipelago ECN®; BEST:Bear, Stearns and Co., Inc.®; BTAB: BT Alex Brown Inc.®; DLJP:Donaldson, Lufkin and Jenrette Securities®; FBCO: Credit Suisse FirstBoston Corporation®; GSCO: Goldman, Sachs and Co.®; HMQT: Hambrecht andQuist LLC®; HRZG: Herzog, Heine, Geduld, Inc.®; INCA: Instinet Corp.(ECN)®; ISLD: The Island ECN®; MASH: Mayer and Schweitzer, Inc.®; MLCO:Merrill Lynch, Pierce, Fenner and Smith Inc.®; MSCO: Morgan Stanley andCo., Inc.®; NITE: Knight Securities, Inc.®; PIPR: US Bancorp PiperJaffray Inc.®; PRUS: Prudential Securities Inc.®; RSSF: BancbostonRobertson Stephens Inc.®; SBSH: Salomon, Smith Barney Inc.®; TNTO: TerraNova Trading, LLC®; TSCO: Troster Singer Corporation®; Direct Edge ECN®;BATS®; Currenex®; Fxall®; eSpeed®; Global Link®; Hotspot®; MilanFX®;NYFIX®; Track ECN®; and Dukascopy®.

Additional Discussion on Sensor Nodes, Motes, Mobile Servers, CellularServers, and Wireless Servers, Wireless Sensors, Wireless SensorNetworks

The client-server multitasking system 10/metasearch system of thepresent invention may be used to request, retrieve and organizeinformation and/or data from multiple devices, wireless devices and/ormultiple wireless servers having multiple data streams, and group and/orsort the information and/or data in real-time and on-the-fly, accordingto information in the user's request and/or data stream identifiers.

A wireless sensor network (WSN) is a wireless network comprisingspatially distributed autonomous devices, using sensors to cooperativelymonitor physical, environmental and/or other conditions at differentlocations. Wireless sensor networks (WSNs) may also be used for trackingand/or control.

Typical applications of WSNs include monitoring, tracking, andcontrolling, and may be used in battlefield surveillance, command andcontrol systems, civilian applications, including environment andhabitat monitoring, healthcare applications, automation, trafficcontrol, and other suitable applications. Other applications includesecurity, intrusion detection, perimeter warning systems, intruderdetection, fire safety, medical monitoring, smart spaces, seismicdetection, monitoring of ice flows and icebergs, military surveillance,inventory tracking, process monitoring, structural systems monitoring,nuclear reactor monitoring, ocean current and wave detection andmonitoring, atmospheric monitoring, monitoring of air, water, and groundpollutants, tracking of people and animals, and numerous other suitableapplications.

A wireless sensor network (WSN) and/or wireless sensor networks (WSNs)may be scattered throughout a region to collect data through its sensornodes.

Information and/or data may be collected for a host of parameters,including, for example, temperature, sound, light, pressure, motion,heat, pressure, sound, light, magnetic fields, electromagnetic fields,vibration, wind speed and direction, and other suitable informationand/or data.

Wireless sensor networks (WSNs) may comprise heterogeneous sensor websand/or homogeneous sensor webs. Heterogeneous sensor webs may have acombination of the same and/or different types of motes, sensors, and/ornodes, whereas homogeneous sensor webs may have substantially the sametypes of motes, sensors, and/or nodes. Wireless sensor networks (WSNs)will often comprise distributed databases.

Wireless sensor networks (WSNs) may be extended to include wirelessrobotic devices, in which in addition to sensing and/or cooperativelymonitoring physical, environmental and/or other conditions at differentlocations, but also to control systems, controlling, moving and/orfollowing commands to move from location to location and/or accomplishmanual and/or mechanical tasks and/or other tasks, requiring a degree ofdexterity and/or combinations thereof.

Certain sensors may be interactive, whereas other sensors may not beinteractive. For those sensors that are interactive, information and/ordata may be retrieved from the interactive sensors and/or via at leastnode or a plurality of nodes that are interactive. For those sensorsthat are not interactive, information and/or data may be retrieved viaat least node or a plurality of nodes that are interactive. A webbrowser or other suitable graphical user interface may be used tomonitor the wireless sensor networks (WSNs).

Miniaturization and low cost are often key ingredients in wirelesssensor networks (WSNs). The size of a single sensor node can vary fromshoebox-sized nodes down to devices the size of a cubic millimeter oreven down the size of a grain of dust. Sensor nodes may be considered tobe small computers or servers, or server devices.

Each sensor node, which may optionally called a mote is a node in thewireless sensor network (WSN) that is often capable of performing someprocessing, gathering sensory information and communicating with otherconnected nodes in the network.

Each sensor node may be considered to be a small computer, server, orserver device. In addition to one or more sensors and/or robots, eachsensor node in a wireless sensor network (WSN) is typically equippedwith a transceiver or other wireless communications device, a smallprocessor, microprocessor, or microcontroller, additional optionalmemory, one or more analog to digital converters, as required, and anenergy source, such as a battery, energy harvesting device, or othersuitable power source. The wireless transceiver may be a radiotransceiver, an optical transceiver, or other suitable wirelesscommunications device or combination thereof. Data transmission isusually multi-hop, i.e., from node to node, towards the base stations,and is often based upon distributed algorithms.

Wireless sensor networks (WSNs) may have one or more gateways, gatewaysensor nodes, or base stations between the sensor nodes and the enduser, and which may have more computational power, energy resources,and/or communication resources than the sensor nodes. The sensor nodesare typically deployed to sense, track, and/or control phenomena, andthe gateway node is typically the interface between the wireless sensornetwork (WSN) and the world external to the wireless sensor network(WSN).

The gateway nodes and/or certain ones of the sensor nodes and/or othersuitable components of the wireless sensor network (WSN) may beconfigured to perform as servers, depending upon the configuration ofthe wireless sensor network (WSN).

Each of the requests Q₁₁ . . . Q_(nm) (29) may then be made of certainones of the same and/or different ones of the gateway nodes and/orcertain ones of the sensor nodes and/or other suitable components of thewireless sensor network (WSN) in the same manner as the requests Q₁₁ . .. Q_(nm) (29) are made of the servers S₁ . . . S_(z) (20), and/or theoptional servers SO₁ . . . SO_(p) (22) of the client-server multitaskingsystem 10/metasearch system.

The client-server multitasking system 10/metasearch system may then beused to process multiple responses from the certain ones of the sameand/or different ones of the gateway nodes and/or the certain ones ofthe sensor nodes and/or the other suitable components of the wirelesssensor network (WSN), and group and sort the results, all in real timeand on-the-fly.

The particular service and/or information request IQ_(n) (28) receivedfrom the corresponding client C_(n) (16) is parsed, processed, and/orformatted by the server PS (18) into the current request group QA_(nc)(50), and information therefrom is used to make the requests Q₁₁ . . .Q_(nm) (29) of the certain ones of the same and/or different ones of thegateway nodes and/or the certain ones of the sensor nodes and/or theother suitable components of the wireless sensor network (WSN), obtainthe responses R_(n1) . . . R_(nm) (32) therefrom, parse, process,format, group, sort, and/or organize the service and/or informationgroup G. (35) having the query information groups GI_(n1) . . . GI_(nz)(63) therein, incorporate information therefrom into the particularservice and/or information response IR_(n) (34), and return theparticular service and/or information response IR_(n) (34) to thecorresponding client C_(n) (16).

Substantially the same system and method that is used to retrieveinformation and/or data for wireless sensor networks (WSNs) may be usedfor other wireless devices and/or RFIDs.

Additional Processing and Add-On Applications

Additional processing and/or add-on applications, such as spreadsheetprograms and/or database applications may be added to the client-servermultitasking system 10, the client-server multitasking process 99,and/or the multitasking process 104, as required.

Additional processing and/or add-on programs and/or applications, suchas spreadsheet programs and/or applications, and/or databaseapplications and/or programs, and/or other suitable processing may beused to further process the output of the client-server multitaskingsystem 10/metasearch system, the client-server multitasking process99/metasearch process, and/or the multitasking process 104/metasearchprocess of the present invention, as required.

Although the present invention has been described in considerable detailwith reference to certain preferred versions thereof, other versions arepossible. Therefore, the spirit and scope of the appended claims shouldnot be limited to the description of the preferred versions containedherein.

1. A process for metasearching on a distributed network activated by arequest executed on a client device to request a metasearch engine tosend at least one search query to a plurality of server devices, the atleast one search query comprising at least one keyword phrase, the atleast one keyword phrase comprising at least one keyword, comprising thesteps of: (a) receiving, at the metasearch engine, the request from theclient device for the metasearch engine to send the at least one searchquery comprising the at least one keyword phrase to the plurality ofserver devices; (b) sending, by the metasearch engine, the at least onesearch query comprising the at least one keyword phrase to the pluralityof server devices; (c) receiving, at the metasearch engine, searchresults from the plurality of server devices in response to the at leastone search query comprising the at least one keyword phrase sent to theplurality of server devices, wherein: at least one of the receivedsearch results comprises information about at least one item that may beordered; (d) incorporating, by the metasearch engine, the receivedsearch results into at least one display list corresponding to the atleast one keyword phrase and incorporating, by the metasearch engine,means for inputting at least one quantity of the at least one item thatmay be ordered into the at least one display list that comprises the atleast one of the received search results comprising the informationabout the at least one item that may be ordered; (e) incorporating, bythe metasearch engine, the at least one display list of received searchresults comprising the means for inputting the at least one quantity ofthe at least one item that may be ordered into a response forcommunicating to the client device and incorporating, by the metasearchengine, into the response for communicating to the client device meansfor placing, by the metasearch engine, at least one order for the atleast one quantity of the at least one item that may be ordered; (f)communicating, by the metasearch engine, the response from themetasearch engine to the client device.
 2. The process of claim 1,wherein the request specifies: the plurality of server devices the atleast one search query is to be sent to.
 3. The process of claim 1,further comprising the step of: (g) receiving, at the metasearch engine,another request from the client device executed on the client device toplace the at least one order for the at least one quantity of the atleast one item; (h) placing, by the metasearch engine, the at least oneorder with at least one server device of the plurality of server devicesand/or at least one third party for the at least one item.
 4. Theprocess of claim 1, wherein step (d) further comprises: sorting, by themetasearch engine, the search results within the at least one displaylist.
 5. The process of claim 1, wherein the at least one item that maybe ordered comprises at least two items that may be ordered and theincorporating, by the metasearch engine, of the received search resultsinto the at least one display list corresponding to the at least onekeyword phrase comprises incorporating the at least two items that maybe ordered into the at least one display list, further comprising thesteps of: (g) receiving, at the metasearch engine, another request fromthe client device executed on the client device to place at least twoorders for the at least two items that may be ordered; (h) placing, bythe metasearch engine, the at least two orders with at least one serverdevice of the plurality of server devices and/or at least one thirdparty for the at least one item.
 6. The process of claim 1, wherein theat least one item that may be ordered comprises at least two items thatmay be ordered and the incorporating, by the metasearch engine, of thereceived search results into the at least one display list correspondingto the at least one keyword phrase comprises incorporating the at leasttwo items that may be ordered into the at least one display list, step(d) further comprises: sorting, by the metasearch engine, the receivedsearch results into the at least one display list according to price ofthe at least two items that may be ordered.
 7. The process of claim 1,wherein the at least one item that may be ordered comprises at least twoitems that may be ordered and the incorporating, by the metasearchengine, of the received search results into the at least one displaylist corresponding to the at least one keyword phrase comprisesincorporating the at least two items that may be ordered into the atleast one display list, step (d) further comprises: sorting, by themetasearch engine, the received search results into the at least onedisplay list in alphanumeric order of the at least two items that may beordered.
 8. The process of claim 5, wherein: the at least one displaylist comprises at least one order book.
 9. The process of claim 1,wherein step (d) further comprises: identifying, by the metasearchengine, the at least one display list with information that identifiesthe at least one keyword phrase the at least one display listcorresponds to; identifying, by the metasearch engine, each of thereceived search results with information that identifies which of theplurality of server devices the received search results were receivedfrom.
 10. The process of claim 1, wherein the at least one item is fromthe group consisting of: at least one item, at least one product, atleast one security, at least one stock, at least one commodity, at leastone currency, at least one financial product, at least one financialinstrument, at least one ticket, at least one airline ticket, at leastone service, information, data, music, audio, video, television, radio,at least on device, at least one apparatus, at least one method, atleast one process, data, at least one file, at least one data file, atleast one computer file, at least one music file, at least one videofile, software, at least one application, at least one softwareapplication, at least one item that can be purchased, at least one itemthat can be shopped, at least one item for which the at least one ordercan be placed, and any combination of one or more thereof.
 11. Theprocess of claim 1, wherein: at least one server device of the pluralityof server devices is from the group consisting of: at least one serverdevice, at least one server, at least one search engine, at least onemetasearch engine, at least one database, at least one database server,at least one data server, at least one file server, at least oneinformation source, at least one site, at least one website, at leastone electronic communication network, at least one ECN, at least one ECNserver device, at least one ECN server, at least one ECN database, atleast one electronic trading system, at least one alternative tradingsystem, at least one computer assisted trading system, at least oneelectronic exchange, at least one electronic stock exchange, at leastone virtual exchange, at least one electronic market, at least oneelectronic stock market, at least one virtual market, at least oneclient device, at least one client, at least one software process, atleast one process, at least one program, at least one software program,at least one application, at least one software application, at leastone computer, at least one laptop computer, at least one personaldigital assistant, at least one peer-to-peer device, at least onepeer-to-peer application, at least one peer-to-peer softwareapplication, at least one communications device, at least onetransceiver, at least one wireless sensor node, at least one mote, atleast one wireless gateway node, at least one wireless computer, atleast one wireless platform, at least one robot, at least one wirelessrobot, at least one mobile server, at least one mobile device, at leastone cellular server, at least one cellular device, at least one cellularphone, at least one cell phone, at least one miniature computer, atleast one nanoscale server, at least one nanoscale computer, at leastone nanocomputer, at least one radio frequency identification device, atleast one newsgroup server, at least one e-mail server, at least onee-mail client, at least one intranet system, at least one personalsearch engine, at least one mobile search engine, at least onedirectory, at least one open directory, at least one web server, atleast one File Transfer Protocol site, at least one FTP site, at leastone FTP server device, at least one FTP server, at least one podcast, atleast one feed, at least one feed aggregator, at least one feed reader,at least one web feed, at least one webcast, at least one XML feed, atleast one newsfeed, at least one newsfeed server, at least one blog, atleast one RSS feed, at least one aggregator, at least one feedaggregator, at least one feed reader, at least one web application, atleast one video blog, at least one advertiser feed, at least oneadvertiser server, at least one syndication server, at least one websyndication server, at least one data stream device, at least onemultiple data stream device, at least one WiFi device, and anycombination thereof, the client device is from the group consisting of:a client device, a client, a server device, a server, a process, aprogram, a software program, an application, a software application, acomputer, a laptop computer, a computer terminal, a communicationsdevice, a transceiver, a personal digital assistant, a peer-to-peerdevice, a peer-to-peer application, a peer-to-peer software application,a wireless device, a wireless computer, a wireless server, a wirelessplatform, a wireless client device, a wireless client, a mobile server,a mobile device, a cellular server, a cellular device, a cellular phone,a cell phone, a miniature computer, a nanoscale server, a nanoscalecomputer, a nanocomputer, a search engine, a metasearch engine, a site,a website, a television, a television device, a display device, aninput-output device, and any combination thereof, the distributednetwork is from the group consisting of: at least one distributednetwork, at lest one network, the internet, at least one interconnectednetwork, at least one global network, at least one global area network,at least one worldwide network, at least one metropolitan area network,at least one wide area network, at least one local area network, atleast one intranet, at least one spatially distributed network, at leastone computer network, at least one network of computers, at least onedistributed database, at least one electronic communication network, atleast one ECN, at least one electronic trading system, at least onealternative trading system, at least one computer assisted tradingsystem, at least one electronic exchange, at least one electronic stockexchange, at least one virtual exchange, at least one electronic market,at least one electronic stock market, at least one virtual market, atleast one wireless network, at least one wireless sensor network, andany combination thereof.
 12. The process of claim 1, wherein step (b)further comprises: sending, by the metasearch engine, the at least onesearch query comprising the at least one keyword phrase substantiallysimultaneously to the plurality of server devices and/or prior tosending, by the metasearch engine, the at least one search querycomprising the at least one keyword phrase to the plurality of serverdevices, opening connections, by the metasearch engine, substantiallysimultaneously with the plurality of server devices.
 13. A system formetasearching on a distributed network activated by a request executedon a client device to request a metasearch engine to send at least onesearch query to a plurality of server devices, the at least one searchquery comprising at least one keyword phrase, the at least one keywordphrase comprising at least one keyword, comprising: (a) means forreceiving, at the metasearch engine, the request from the client devicefor the metasearch engine to send the at least one search querycomprising the at least one keyword phrase to the plurality of serverdevices; (b) means for sending, by the metasearch engine, the at leastone search query comprising the at least one keyword phrase to theplurality of server devices; (c) means for receiving, at the metasearchengine, search results from the plurality of server devices in responseto the at least one search query comprising the at least one keywordphrase sent to the plurality of server devices, wherein: at least one ofthe received search results comprises information about at least oneitem that may be ordered; (d) means for incorporating, by the metasearchengine, the received search results into at least one display listcorresponding to the at least one keyword phrase and means forincorporating, by the metasearch engine, means for inputting at leastone quantity of the at least one item that may be ordered into the atleast one display list that comprises the at least one of the receivedsearch results comprising the information about the at least one itemthat may be ordered; (e) means for incorporating, by the metasearchengine, the at least one display list of received search resultscomprising the means for inputting the at least one quantity of the atleast one item that may be ordered into a response for communicating tothe client device and incorporating, by the metasearch engine, into theresponse for communicating to the client device means for placing, bythe metasearch engine, at least one order for the at least one quantityof the at least one item that may be ordered; (f) means forcommunicating, by the metasearch engine, the response from themetasearch engine to the client device.
 14. The system of claim 13,further comprising: (g) means for receiving, at the metasearch engine,another request from the client device executed on the client device toplace the at least one order for the at least one quantity of the atleast one item; (h) means for placing, by the metasearch engine, the atleast one order with at least one server device of the plurality ofserver devices and/or at least one third party for the at least oneitem.
 15. The system of claim 13, further comprising: means for sorting,by the metasearch engine, the search results within the at least onedisplay list.
 16. A computer readable storage medium containing computerexecutable instructions for metasearching on a distributed networkactivated by a request executed on a client device to request ametasearch engine to send at least one search query to a plurality ofserver devices, the at least one search query comprising at least onekeyword phrase, the at least one keyword phrase comprising at least onekeyword, causing one or more computers to: (a) receive, at themetasearch engine, the request from the client device for the metasearchengine to send the at least one search query comprising the at least onekeyword phrase to the plurality of server devices; (b) send, by themetasearch engine, the at least one search query comprising the at leastone keyword phrase to the plurality of server devices; (c) receive, atthe metasearch engine, search results from the plurality of serverdevices in response to the at least one search query comprising the atleast one keyword phrase sent to the plurality of server devices,wherein: at least one of the received search results comprisesinformation about at least one item that may be ordered; (d)incorporate, by the metasearch engine, the received search results intoat least one display list corresponding to the at least one keywordphrase and incorporate, by the metasearch engine, means for inputting atleast one quantity of the at least one item that may be ordered into theat least one display list that comprises the at least one of thereceived search results comprising the information about the at leastone item that may be ordered; (e) incorporate, by the metasearch engine,the at least one display list of received search results comprising themeans for inputting the at least one quantity of the at least one itemthat may be ordered into a response for communicating to the clientdevice and incorporating, by the metasearch engine, into the responsefor communicating to the client device means for placing, by themetasearch engine, at least one order for the at least one quantity ofthe at least one item that may be ordered; (f) communicate, by themetasearch engine, the response from the metasearch engine to the clientdevice.
 17. The computer readable storage medium containing computerexecutable instructions of claim 16, further causing one or morecomputers to: receive, at the metasearch engine, another request fromthe client device executed on the client device to place the at leastone order for the at least one quantity of the at least one item; place,by the metasearch engine, the at least one order with at least oneserver device of the plurality of server devices and/or at least onethird party for the at least one item.
 18. The computer readable storagemedium containing computer executable instructions of claim 16, furthercausing one or more computers at (d) to: sort, by the metasearch engine,the search results within the at least one display list.
 19. Anapparatus for metasearching on a distributed network activated by arequest executed on a client device to request a metasearch engine tosend at least one search query to a plurality of server devices, the atleast one search query comprising at least one keyword phrase, the atleast one keyword phrase comprising at least one keyword, comprising:(a) a receiver receiving, at the metasearch engine, the request from theclient device for the metasearch engine to send the at least one searchquery comprising the at least one keyword phrase to the plurality ofserver devices; (b) a sender sending, by the metasearch engine, the atleast one search query comprising the at least one keyword phrase to theplurality of server devices; (c) the receiver receiving, at themetasearch engine, search results from the plurality of server devicesin response to the at least one search query comprising the at least onekeyword phrase sent to the plurality of server devices, wherein: atleast one of the received search results comprises information about atleast one item that may be ordered; (d) an incorporator incorporating,by the metasearch engine, the received search results into at least onedisplay list corresponding to the at least one keyword phrase and theincorporator incorporating, by the metasearch engine, means forinputting at least one quantity of the at least one item that may beordered into the at least one display list that comprises the at leastone of the received search results comprising the information about theat least one item that may be ordered; (e) the incorporatorincorporating, by the metasearch engine, the at least one display listof received search results comprising the means for inputting the atleast one quantity of the at least one item that may be ordered into aresponse for communicating to the client device and incorporating, bythe metasearch engine, into the response for communicating to the clientdevice means for placing, by the metasearch engine, at least one orderfor the at least one quantity of the at least one item that may beordered; (f) a communicator communicating, by the metasearch engine, theresponse from the metasearch engine to the client device.
 20. Theapparatus of claim 19, further comprising: (g) the receiver receiving,at the metasearch engine, another request from the client deviceexecuted on the client device to place the at least one order for the atleast one quantity of the at least one item; (h) a placer placing, bythe metasearch engine, the at least one order with at least one serverdevice of the plurality of server devices and/or at least one thirdparty for the at least one item.
 21. The apparatus of claim 22, furthercomprising: a sorter sorting, by the metasearch engine, the searchresults within the at least one display list.
 22. A process formetasearching on a distributed network activated by a request executedon a client device to request a metasearch engine to send at least onesearch query to a plurality of server devices, the at least one searchquery comprising at least one keyword phrase, the at least one keywordphrase comprising at least one keyword, comprising the steps of: (a)receiving, at the metasearch engine, the request from the client devicefor the metasearch engine to send the at least one search querycomprising the at least one keyword phrase to the plurality of serverdevices; (b) sending, by the metasearch engine, the at least one searchquery comprising the at least one keyword phrase to the plurality ofserver devices; (c) receiving, at the metasearch engine, search resultsfrom the plurality of server devices in response to the at least onesearch query comprising the at least one keyword phrase sent to theplurality of server devices, wherein: at least one of the receivedsearch results comprises information about at least one item that may beordered; (d) incorporating, by the metasearch engine, the receivedsearch results into at least one display list corresponding to the atleast one keyword phrase, the at least one display list comprising theinformation about the at least one item that may be ordered; (e)incorporating, by the metasearch engine, the at least one display listof received search results comprising the information about the at leastone item that may be ordered into a response for communicating to theclient device and incorporating, by the metasearch engine, into theresponse for communicating to the client device means for placing, bythe metasearch engine, at least one order for the at least one quantityof the at least one item that may be ordered; (f) communicating, by themetasearch engine, the response from the metasearch engine to the clientdevice.
 23. The process of claim 22, further comprising the step of: (g)receiving, at the metasearch engine, another request from the clientdevice executed on the client device to place the at least one order forthe at least one quantity of the at least one item; (h) placing, by themetasearch engine, the at least one order with at least one serverdevice of the plurality of server devices and/or at least one thirdparty for the at least one item.
 24. The process of claim 22, whereinstep (d) further comprises: sorting, by the metasearch engine, thesearch results within the at least one display list.
 25. The process ofclaim 22, wherein the at least one item that may be ordered comprises atleast two items that may be ordered and the incorporating, by themetasearch engine, of the received search results into the at least onedisplay list corresponding to the at least one keyword phrase comprisesincorporating the at least two items that may be ordered into the atleast one display list, further comprising the steps of: (g) receiving,at the metasearch engine, another request from the client deviceexecuted on the client device to place at least two orders for the atleast two items that may be ordered; (h) placing, by the metasearchengine, the at least two orders with at least one server device of theplurality of server devices and/or at least one third party for the atleast one item.